Copy a sheet to another Google Sheets spreadsheet
AI agents use sheets_copy_to to create or update resources in MCP Google Sheets Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Sheets Server environment.
The tool creates or duplicates data in a target Google Sheets spreadsheet. While the source sheet remains unchanged, the copy operation modifies the destination spreadsheet by adding new sheet content. This is reversible (the copied sheet can be deleted), making it a Write rather than Destructive action.
From the tool's definition Tool name 'sheets_copy_to' and description 'Copy a sheet to another Google Sheets spreadsheet' indicate creation/replication of data in a destination spreadsheet. This is a reversible write operation.
Attacks that exploit this kind of access
Copy a sheet to another Google Sheets spreadsheet. It is categorised as a Write tool in the MCP Google Sheets Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Sheets Server MCP server in PolicyLayer and add a rule for sheets_copy_to: 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 Server. Nothing to install.
sheets_copy_to 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 sheets_copy_to 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 sheets_copy_to. 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.
sheets_copy_to is provided by the MCP Google Sheets Server MCP server (oregpt/agenticledger_mcp_sheetsonly). 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 →