Skip to main content
Book a demo

Connect Google Drive to Cursor

Give Cursor governed access to Google Drive’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Google Drive to Cursor in four steps

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

  1. 1

    Approve Google Drive in Runlayer

    Add Google Drive 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, Google Drive’s 16 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Google Drive

    Sign in the way Google Drive requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Google Drive from Cursor

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

Tools

16 Google Drive tools in Cursor

Runlayer policy decides which of these Cursor users can call. 5 read data only and 1 can change or delete data.

  • Copy file

    Create a copy of a file in Google Drive.

  • Create doc from markdown

    Create a beautifully formatted Google Doc from markdown content.

  • Create file

    Create a new file in Google Drive with text or base64-encoded content.

  • Create folder

    Create a new folder in Google Drive to organize files.

  • Delete file

    Delete a file or folder by moving it to trash.

  • Fetch file

    Fetch a file from Google Drive using its Google Drive file ID (don't use exa nor brave to read files).

  • Get metadata

    Get detailed metadata about a specific file or folder, including size, ownership, sharing status, modification dates, and more.

  • List folder

    List all files and folders within a specific folder.

See all 16 Google Drive 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 Google Drive 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