Connect Google Docs to Windsurf
Give Windsurf governed access to Google Docs’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Docs to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Approve Google Docs in Runlayer
Add Google Docs 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 Docs’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 3
Sign in to Google Docs
Sign in the way Google Docs requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Google Docs from Windsurf
Google Docs’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
21 Google Docs tools in Windsurf
Runlayer policy decides which of these Windsurf users can call. 7 read data only and 5 can change or delete data.
Add comment
Add a comment to a specific text range in a Google Docs document.
Apply doc updates
Apply an ordered batch of raw Google Docs API Request objects to a document via documents.batchUpdate.
Create file
Markdown (recommended, default path): uploaded as text/markdown and converted by Google Drive's native markdown importer (headers, bold, italic, lists, tables, blockquotes, fenced code blocks, links,…
Delete between text
Delete a whole block of a document — a heading and everything beneath it, tables included — by naming the text at each end instead of computing character indices.
Delete text
Delete all occurrences of specific text from a Google Docs document.
Edit table
Structurally edit an existing table in a Google Doc: insert/delete rows and columns, set a column width, style a cell (background color, vertical alignment, padding), replace a cell's text, or…
Fetch
Fetch the content of a Google Docs document using its document ID.
Fetch all tabs
Fetch content from all tabs in a Google Docs document.
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 Docs 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