addSheet
Alias for addSpreadsheetSheet (adds a new sheet/tab)
This record as markdown: /tools/ark7-google-drive-mcp/addsheet.md
What addSheet does on Google Drive
AI agents use addSheet 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 |
|---|---|---|---|
title | string | Yes | Title for the new sheet/tab |
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 |
spreadsheetId | string | Yes | Spreadsheet ID |
Parameters from the server's own tool schema.
Why addSheet is rated Medium
Adding a new sheet to a Google Sheet is a data creation action that modifies the spreadsheet structure but is easily undone (sheets can be deleted). This does not permanently destroy data, execute arbitrary code, trigger external side effects, or involve financial transactions. It fits the Write category as a reversible modification.
From the tool's definition Tool description explicitly states it 'adds a new sheet/tab' to a spreadsheet. The verb 'add' and the functional outcome of creating a new sheet constitute a reversible write operation.
Attacks that exploit this kind of access
The rule that runs addSheet 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 addSheet, this is the rule to start with:
addSheet 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 addSheet call is checked against it from then on.
Questions about addSheet
Alias for addSpreadsheetSheet (adds a new sheet/tab). 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.
addSheet accepts 3 parameters: title, account, spreadsheetId. Required: title, 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 addSheet: 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.
addSheet 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 addSheet 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 addSheet. 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.
addSheet 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