replace_named_range_content · Google MCP: Risk & Policy

WHAT IT DOES

What replace_named_range_content does on Google

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

This tool modifies Google Docs content by replacing text within a named range. This is a reversible operation (can be undone or overwritten), making it Write rather than Destructive. The severity is medium because misuse could corrupt document templates or overwrite important content, but the operation remains reversible and doesn't permanently delete data or execute arbitrary code.

From the tool's definition Tool performs 'Replace the content of a named range in a Google Doc' — this modifies document content reversibly. The description explicitly states it replaces content, which is a Write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replace_named_range_content Rate-limited

replace_named_range_content 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": {
    "replace_named_range_content": {
      "limits": [
        {
          "counter": "replace_named_range_content_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 replace_named_range_content

What does the replace_named_range_content tool do? +

Replace the content of a named range in a Google Doc (useful for templates). 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 replace_named_range_content? +

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

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

Can I rate-limit replace_named_range_content? +

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

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

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