New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

renameSheet

Rename a sheet/tab by sheetId

SERVERGoogle Drive SOURCE@ark7/google-drive-mcp
Medium RISK CLASS
Category Write
Parameters 43 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about renameSheet

What does the renameSheet tool do? +

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.

What parameters does renameSheet accept? +

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.

How do I enforce a policy on renameSheet? +

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.

What risk level is renameSheet? +

renameSheet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit renameSheet? +

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.

How do I block renameSheet completely? +

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.

What MCP server provides renameSheet? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Drive's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.