Add a new sheet to an existing Google Sheets spreadsheet
AI agents use sheets_insert_sheet to create or update resources in Mcp Gsheets — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gsheets environment.
This tool creates a new sheet within a spreadsheet, which is a reversible Write operation. It modifies the spreadsheet structure by adding a new sheet but does not delete data or execute arbitrary code. The severity is medium because inserting unwanted sheets could clutter a spreadsheet or cause confusion, but the operation is easily reversible (sheets can be deleted).
From the tool's definition Tool name 'sheets_insert_sheet' combined with description 'Add a new sheet to an existing Google Sheets spreadsheet' clearly indicates a sheet creation operation.
Attacks that exploit this kind of access
Add a new sheet to an existing Google Sheets spreadsheet. It is categorised as a Write tool in the Mcp Gsheets MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gsheets MCP server in PolicyLayer and add a rule for sheets_insert_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 Gsheets. Nothing to install.
sheets_insert_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 sheets_insert_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 sheets_insert_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.
sheets_insert_sheet is provided by the Mcp Gsheets MCP server (mcp-gsheets). 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 →