create_spreadsheet_from_existing
Create a new google sheets spreadsheet by copying an existing one.
This record as markdown: /tools/dev-ithitchhiker-mcp-google-docs/create-spreadsheet-from-existing.md
What create_spreadsheet_from_existing does on Mcp Google Docs
AI agents use create_spreadsheet_from_existing to create or update resources in Mcp Google Docs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Docs environment.
Why create_spreadsheet_from_existing is rated Medium
This tool creates new resources (a copied spreadsheet) in the user's Google Drive, which is a reversible write operation. It does not delete, destroy, or execute arbitrary code. The severity is medium because while the operation is reversible and the blast radius is limited to storage quota and organizational structure, creating many copies could impact storage and permissions management.
From the tool's definition Tool creates a new spreadsheet by copying an existing one. The description explicitly states 'Create a new google sheets spreadsheet', which is a write operation that creates new data/resources in Google Drive.
Attacks that exploit this kind of access
The rule that runs create_spreadsheet_from_existing safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_spreadsheet_from_existing, this is the rule to start with:
create_spreadsheet_from_existing 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 Mcp Google Docs, apply this rule, and every create_spreadsheet_from_existing call is checked against it from then on.
Questions about create_spreadsheet_from_existing
Create a new google sheets spreadsheet by copying an existing one. It is categorised as a Write tool in the Mcp Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for create_spreadsheet_from_existing: 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 Docs. Nothing to install.
create_spreadsheet_from_existing 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 create_spreadsheet_from_existing 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 create_spreadsheet_from_existing. 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.
create_spreadsheet_from_existing is provided by the Mcp Google Docs MCP server (dev-ithitchhiker/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Docs, and thousands of servers like it.
This server
Across the catalogue