Shares the provided spreadsheet to the recipients provided as an argument. Accepts recipients as an array of objects in the form of {email_address, role}. Also, sends a notification email to the users informing them about the access granted to them.
AI agents use shareSpreadsheet to create or update resources in Mcp Google Sheets — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Sheets environment.
shareSpreadsheet modifies access control and permissions on a spreadsheet by granting roles to recipients. This is a Write operation because permission changes are reversible (access can be removed later). It is not Destructive because no data is deleted or permanently lost.
From the tool's definition The tool 'shares the provided spreadsheet to the recipients' and 'sends a notification email to the users', which are reversible modifications (sharing permissions can be revoked, emails sent but are informational).
Documented attack patterns abuse exactly the kind of access shareSpreadsheet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Google Sheets, and nothing reaches the server without passing your rules. This is the rule we recommend for shareSpreadsheet:
{
"version": "1",
"default": "deny",
"tools": {
"shareSpreadsheet": {
"limits": [
{
"counter": "sharespreadsheet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}shareSpreadsheet stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Shares the provided spreadsheet to the recipients provided as an argument. Accepts recipients as an array of objects in the form of {email_address, role}. Also, sends a notification email to the users informing them about the access granted to them. It is categorised as a Write tool in the Mcp Google Sheets MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Google Sheets MCP server in PolicyLayer and add a rule for shareSpreadsheet: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Google Sheets. Nothing to install.
shareSpreadsheet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the shareSpreadsheet rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for shareSpreadsheet. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
shareSpreadsheet is provided by the Mcp Google Sheets MCP server (rohans2/mcp-google-sheets). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Google Sheets, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Mcp Google Sheets tools catalogued and risk-classified — across an index of 43,000+ MCP servers.