Rename an existing sheet tab in a Google Sheets spreadsheet.
AI agents use gdrive_rename_sheet_tab to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.
Renaming a sheet tab modifies metadata in a Google Sheets file, but the change is reversible—the user can rename it back or undo via Google Sheets history. This is a Write action, not Destructive (no data loss) and not Execute (no code/command execution).
From the tool's definition Tool description states 'Rename an existing sheet tab' — a modification operation. The sibling tools on this server include destructive operations (delete_doc_text, delete_rows_columns, delete_sheet_tab), and this tool falls into the reversible modification…
Attacks that exploit this kind of access
Rename an existing sheet tab in a Google Sheets spreadsheet. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for gdrive_rename_sheet_tab: 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 MCP Server. Nothing to install.
gdrive_rename_sheet_tab 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 gdrive_rename_sheet_tab 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 gdrive_rename_sheet_tab. 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.
gdrive_rename_sheet_tab is provided by the Google Drive MCP Server MCP server (wagnerlabs/gdrive-mcp). 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 →