Copy a worksheet to the same or a different spreadsheet.
AI agents use copy_worksheet to create or update resources in Google Connections — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Connections environment.
Copying a worksheet creates new data structures and content in the destination location. While reversible (the copy can be deleted), it represents data creation/modification rather than mere retrieval (Read). It does not execute arbitrary code (Execute), permanently destroy data (Destructive), or move money (Financial).
From the tool's definition Tool description states it 'Copy[ies] a worksheet' which creates a new copy of worksheet data in the same or different spreadsheet. This is a reversible modification operation.
Attacks that exploit this kind of access
Copy a worksheet to the same or a different spreadsheet. It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Connections MCP server in PolicyLayer and add a rule for copy_worksheet: 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 Google Connections. Nothing to install.
copy_worksheet 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 copy_worksheet 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 copy_worksheet. 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.
copy_worksheet is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). 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 →