copySheetTo
Copies a sheet (tab) from one spreadsheet to another spreadsheet. Use getSpreadsheetInfo to find the numeric sheet ID. The copied sheet will be appended to the destination spreadsheet.
This record as markdown: /tools/a-bonus-google-docs-mcp/copysheetto.md
What copySheetTo does on Claude MCP x Google Docs
AI agents use copySheetTo to create or update resources in Claude MCP x Google Docs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude MCP x Google Docs environment.
Why copySheetTo is rated Medium
This tool creates or modifies data reversibly by copying sheet structure and content to another spreadsheet. While it appends data (a write operation), it does not delete or irreversibly destroy anything, nor does it execute arbitrary code or move money. The operation can be undone by deleting the copied sheet, making it Write rather than Destructive.
From the tool's definition Tool description states it 'Copies a sheet (tab) from one spreadsheet to another spreadsheet' and 'appended to the destination spreadsheet', indicating creation of new data in the destination.
Attacks that exploit this kind of access
The rule that runs copySheetTo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP x Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For copySheetTo, this is the rule to start with:
copySheetTo 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude MCP x Google Docs, apply this rule, and every copySheetTo call is checked against it from then on.
Questions about copySheetTo
Copies a sheet (tab) from one spreadsheet to another spreadsheet. Use getSpreadsheetInfo to find the numeric sheet ID. The copied sheet will be appended to the destination spreadsheet. It is categorised as a Write tool in the Claude MCP x Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude MCP x Google Docs MCP server in PolicyLayer and add a rule for copySheetTo: 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 Claude MCP x Google Docs. Nothing to install.
copySheetTo 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 copySheetTo 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 copySheetTo. 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.
copySheetTo is provided by the Claude MCP x Google Docs MCP server (a-bonus/google-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude MCP x Google Docs, and thousands of servers like it.
This server
Across the catalogue