replace_range

SERVERMcp Google Docs SOURCE@a1-x-tech/mcp-google-docs

Medium RISK CLASS

Category Write

Parameters 64 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a1-x-tech-mcp-google-docs/replace-range.md

WHAT IT DOES

What replace_range does on Mcp Google Docs

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

Parameter	Type	Required	Description
`text`	string	Yes	The replacement text; empty string just deletes the range.
`tab_id`	string	—	Tab to target (from list_tabs). Omit for the first/only tab.
`end_index`	integer	Yes	End of the range to replace (exclusive).
`segment_id`	string	—	Header/footer/footnote segment id (from get_document). Omit for the document body.
`document_id`	string	Yes	The document id — the long id from the document URL (docs.google.com/document/d/<documentId>/edit) or from create_document output.
`start_index`	integer	Yes	Start of the range to replace (inclusive).

Parameters from the server's own tool schema.

RISK

Why replace_range is rated Medium

An AI agent can call replace_range faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Docs by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs replace_range safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replace_range, this is the rule to start with:

replace_range Rate-limited

replace_range 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_range": {
      "limits": [
        {
          "counter": "replace_range_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Docs, apply this rule, and every replace_range call is checked against it from then on.

FAQ

Questions about replace_range

What does the replace_range tool do? +

Replaces the content in [start_index, end_index) with new text — one atomic batchUpdate that deletes the range and inserts at its start, so nothing is lost if either step would fail. Get fresh indexes from read_document_text first: indexes are stale after ANY previous edit. The new text takes the style at start_index. Cannot cut across a table cell boundary or delete a paragraph's final newline together with only part of the next paragraph — the API rejects such ranges. An empty replacement is allowed and equals delete_range. It is categorised as a Write tool in the Mcp Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does replace_range accept? +

replace_range accepts 6 parameters: text, tab_id, end_index, segment_id, document_id, start_index. Required: text, end_index, document_id, start_index. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on replace_range? +

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

What risk level is replace_range? +

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

Can I rate-limit replace_range? +

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

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

replace_range is provided by the Mcp Google Docs MCP server (@a1-x-tech/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Google Docs, and thousands of servers like it.

This server

All 27 Mcp Google Docs tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →