rename_doc_tab · Google MCP: Risk & Policy

WHAT IT DOES

What rename_doc_tab does on Google

AI agents use rename_doc_tab to create or update resources in Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google environment.

WHY IT NEEDS A POLICY

Why rename_doc_tab needs a policy

Renaming a document tab modifies the document's structure but is fully reversible (the tab can be renamed again). This is a write operation with no permanent data loss or external side effects. Severity is medium because renaming tabs could confuse collaborators or break references if done maliciously, but the impact is contained to document metadata and easily undone.

From the tool's definition Tool description states "Rename a tab in a Google Doc" — renaming is a reversible modification of document structure/metadata. The server description emphasizes "read/write access" including "structure" changes to Google Docs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_doc_tab Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_doc_tab": {
      "limits": [
        {
          "counter": "rename_doc_tab_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google, so you can run agents against it safely.

FAQ

Questions about rename_doc_tab

What does the rename_doc_tab tool do? +

Rename a tab in a Google Doc. Use list_doc_tabs to find tab IDs. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_doc_tab? +

Register the Google MCP server in PolicyLayer and add a rule for rename_doc_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. Nothing to install.

What risk level is rename_doc_tab? +

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

Can I rate-limit rename_doc_tab? +

Yes. Add a rate_limit block to the rename_doc_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.

How do I block rename_doc_tab completely? +

Set action: deny in the PolicyLayer policy for rename_doc_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.

What MCP server provides rename_doc_tab? +

rename_doc_tab is provided by the Google MCP server (ztgluis/google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.