Skip to main content
Book a demo

Connect Microsoft OneDrive to Cursor

Give Cursor governed access to Microsoft OneDrive’s 11 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Microsoft OneDrive to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 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. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Microsoft OneDrive’s 11 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 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. 4

    Use Microsoft OneDrive from Cursor

    Microsoft OneDrive’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

11 Microsoft OneDrive tools in Cursor

Runlayer policy decides which of these Cursor 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.

See all 11 Microsoft OneDrive tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every Microsoft OneDrive call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination