addSpreadsheetSheet
Adds a new sheet/tab to an existing Google Spreadsheet
This record as markdown: /tools/ark7-google-drive-mcp/addspreadsheetsheet.md
What addSpreadsheetSheet does on Google Drive
AI agents use addSpreadsheetSheet to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
sheetTitle | string | Yes | Title for the new sheet/tab |
spreadsheetId | string | Yes | The ID of the Google Spreadsheet (from the URL) |
Parameters from the server's own tool schema.
Why addSpreadsheetSheet is rated Medium
This tool creates a new sheet within an existing spreadsheet, which is a reversible modification (sheets can be deleted). It does not read-only, does not execute arbitrary code, does not permanently destroy data, and does not involve financial transactions.
From the tool's definition The tool 'addSpreadsheetSheet' 'Adds a new sheet/tab to an existing Google Spreadsheet' - this creates new data structures within a document, modifying the spreadsheet reversibly.
Attacks that exploit this kind of access
The rule that runs addSpreadsheetSheet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For addSpreadsheetSheet, this is the rule to start with:
addSpreadsheetSheet 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 Google Drive, apply this rule, and every addSpreadsheetSheet call is checked against it from then on.
Questions about addSpreadsheetSheet
Adds a new sheet/tab to an existing Google Spreadsheet. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
addSpreadsheetSheet accepts 3 parameters: account, sheetTitle, spreadsheetId. Required: sheetTitle, spreadsheetId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for addSpreadsheetSheet: 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 Google Drive. Nothing to install.
addSpreadsheetSheet 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 addSpreadsheetSheet 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 addSpreadsheetSheet. 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.
addSpreadsheetSheet is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue