Connect Google Sheets to Goose
Give Goose governed access to Google Sheets’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Sheets to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Google Sheets in Runlayer
Add Google Sheets 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 Google Sheets’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Google Sheets
Sign in the way Google Sheets requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Google Sheets from Goose
Google Sheets’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
21 Google Sheets tools in Goose
Runlayer policy decides which of these Goose users can call. 4 read data only and 4 can change or delete data.
Add sheet
Add a new sheet (tab) to an existing spreadsheet.
Append
Append data to a spreadsheet.
Autofill
Extend a formula or detected series from a source range into a larger destination range (like dragging the fill handle).
Clear
Clear the values in a range while leaving the rows, columns, and formatting in place.
Clear filter
Remove a sheet's filter, restoring any rows it was hiding.
Create
Create a new spreadsheet.
Create filter
Turn on filtering over a range of a sheet (the funnel button in the Sheets UI), so rows can be sorted and filtered by column.
Delete rows
Delete rows from a sheet, shifting the rows below them up.
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 Google Sheets 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