Copy a sheet from one spreadsheet to another.
AI agents use copy_sheet 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.
This tool creates or duplicates data across spreadsheets, which is a Write operation (creates new data reversibly). It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). While it modifies spreadsheet structure, the action is reversible—the copied sheet can be deleted.
From the tool's definition Tool description states 'Copy a sheet from one spreadsheet to another' - this creates a new sheet (copy) in a target spreadsheet, which is a reversible modification of data structure and contents.
Attacks that exploit this kind of access
Copy a sheet from one spreadsheet to another. 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 copy_sheet: 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.
copy_sheet 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_sheet 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_sheet. 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_sheet 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 →