Connect Microsoft OneDrive to Goose
Give Goose governed access to Microsoft OneDrive’s 11 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft OneDrive to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Microsoft OneDrive in Runlayer
Add Microsoft OneDrive from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Microsoft OneDrive’s 11 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Microsoft OneDrive
Sign in the way Microsoft OneDrive requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Microsoft OneDrive from Goose
Microsoft OneDrive’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
11 Microsoft OneDrive tools in Goose
Runlayer policy decides which of these Goose users can call. 5 read data only and 1 can change or delete data.
Create folder
Create a new folder in OneDrive.
Create share link
Create a shareable link for a OneDrive item.
Delete item
Delete a OneDrive item (file or folder) by id.
Get item
Fetch metadata for a single OneDrive item (file or folder) by id.
List items
List the immediate children of a OneDrive folder.
List shared with me
List items that other users have shared with the caller via OneDrive, including files in SharePoint document libraries.
Move item
Move a file or folder to a different folder within the user's OneDrive.
Read file
Download a OneDrive file by id and return its text.
Control
What Runlayer can see and stop in Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every Microsoft OneDrive call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more