gdrive_replace_doc_text · Google Drive MCP Server MCP

WHAT IT DOES

What gdrive_replace_doc_text does on Google Drive MCP Server

AI agents use gdrive_replace_doc_text 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.

WHY IT NEEDS A POLICY

Why gdrive_replace_doc_text needs a policy

This tool modifies existing Google Documents by replacing text ranges. While the operation is reversible (users can undo or restore previous versions), it constitutes a Write operation as it alters document content.

From the tool's definition Tool name contains 'replace' and description states 'Replace a targeted text range in an existing Google Doc', which modifies document content. The description explicitly mentions replacing text, which is a write operation that changes existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gdrive_replace_doc_text Rate-limited

gdrive_replace_doc_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": {
    "gdrive_replace_doc_text": {
      "limits": [
        {
          "counter": "gdrive_replace_doc_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 Drive MCP Server, so you can run agents against it safely.

FAQ

Questions about gdrive_replace_doc_text

What does the gdrive_replace_doc_text tool do? +

Replace a targeted text range in an existing Google Doc. Use target_text for anchored replacements or explicit start_index/end_index as a fallback. 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.

How do I enforce a policy on gdrive_replace_doc_text? +

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

What risk level is gdrive_replace_doc_text? +

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

Can I rate-limit gdrive_replace_doc_text? +

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

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

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