Connect Google Drive to Windsurf
Give Windsurf governed access to Google Drive’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Drive to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 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
Connect Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Google Drive’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 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
Use Google Drive from Windsurf
Google Drive’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
16 Google Drive tools in Windsurf
Runlayer policy decides which of these Windsurf 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.
Control
What Runlayer can see and stop in Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Google Drive call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf 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 Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more