This record as markdown: /tools/ark7-google-drive-mcp/renamesheet.md
What renameSheet does on Google Drive
AI agents use renameSheet 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 |
sheetId | number | Yes | Sheet ID |
newTitle | string | Yes | New title |
spreadsheetId | string | Yes | Spreadsheet ID |
Parameters from the server's own tool schema.
Why renameSheet is rated Medium
The renameSheet tool modifies spreadsheet structure by renaming a sheet, which is a Write operation (create/modify data reversibly). It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). The severity is medium because renaming sheets can disrupt workflows and references if done maliciously, but the action is reversible through renaming again.
From the tool's definition Tool description: 'Rename a sheet/tab by sheetId' — renaming is a reversible modification of metadata.
Attacks that exploit this kind of access
The rule that runs renameSheet 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 renameSheet, this is the rule to start with:
renameSheet 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 renameSheet call is checked against it from then on.
Questions about renameSheet
Rename a sheet/tab by sheetId. 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.
renameSheet accepts 4 parameters: account, sheetId, newTitle, spreadsheetId. Required: sheetId, newTitle, 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 renameSheet: 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.
renameSheet 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 renameSheet 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 renameSheet. 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.
renameSheet 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