gdoc_replace_all_text · Google Docs MCP: Risk & Policy

WHAT IT DOES

What gdoc_replace_all_text does on Google Docs

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

WHY IT NEEDS A POLICY

Why gdoc_replace_all_text needs a policy

This tool modifies document content in place across the entire document, which is a Write operation (reversible via undo/version history in Google Docs). However, the blanket replacement of all matching text across a large document could have significant unintended consequences if an AI agent uses overly broad search patterns, potentially corrupting document semantics or data.

From the tool's definition Tool name 'gdoc_replace_all_text' and description 'Find and replace all occurrences of text in the entire document' indicate bulk modification of document content.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gdoc_replace_all_text Rate-limited

gdoc_replace_all_text 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": {
    "gdoc_replace_all_text": {
      "limits": [
        {
          "counter": "gdoc_replace_all_text_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 Docs, so you can run agents against it safely.

FAQ

Questions about gdoc_replace_all_text

What does the gdoc_replace_all_text tool do? +

Find and replace all occurrences of text in the entire document. It is categorised as a Write tool in the Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gdoc_replace_all_text? +

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

What risk level is gdoc_replace_all_text? +

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

Can I rate-limit gdoc_replace_all_text? +

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

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

gdoc_replace_all_text is provided by the Google Docs MCP server (node2flow-th/google-docs-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.