share_spreadsheet
AI agents use share_spreadsheet 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.
Sharing a spreadsheet changes access control and visibility—a reversible modification action (Write category). Severity is high because improper sharing could expose sensitive data to unintended parties, creating compliance and privacy risks for the spreadsheet owner, though the action itself is not destructive or financial. Confidence is 0.75 due to empty tool description; inferred from name and server context.
From the tool's definition Tool name 'share_spreadsheet' indicates modification of access permissions on a spreadsheet resource. Server description mentions 'managing spreadsheet data,' and this tool modifies sharing/permission metadata.
Attacks that exploit this kind of access
share_spreadsheet. 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 share_spreadsheet: 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.
share_spreadsheet 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 share_spreadsheet 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 share_spreadsheet. 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.
share_spreadsheet is provided by the Mcp Google Sheets MCP server (yardobr/mcp-google-sheets). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →