rename_doc · Google MCP: Risk & Policy

WHAT IT DOES

What rename_doc does on Google

AI agents use rename_doc 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 needs a policy

Renaming a document is a reversible write operation that modifies metadata without altering content or triggering destructive effects. The change can be easily undone by renaming again. While it affects an existing resource, it does not delete, permanently destroy data, execute code, or create financial obligations. This is a straightforward Write-category action.

From the tool's definition Tool name 'rename_doc' and description 'Rename a Google Doc file' indicate metadata modification of an existing document.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_doc Rate-limited

rename_doc 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": {
      "limits": [
        {
          "counter": "rename_doc_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

What does the rename_doc tool do? +

Rename a Google Doc file. 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? +

Register the Google MCP server in PolicyLayer and add a rule for rename_doc: 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? +

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

Can I rate-limit rename_doc? +

Yes. Add a rate_limit block to the rename_doc 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 completely? +

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

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