New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

replace_all_text

Replaces EVERY occurrence of a literal string (no regex) across the whole document, or only in the tabs named by tab_ids. match_case defaults to true. Returns occurrencesChanged in the batchUpdate reply — 0 means the text was not found, not an error. Safer than replace_range for textual substitut...

SERVERMcp Google Docs SOURCE@a1-x-tech/mcp-google-docs
Medium RISK CLASS
Category Write
Parameters 53 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-all-text.md

What replace_all_text does on Mcp Google Docs

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

ParameterTypeRequiredDescription
find string Yes The literal text to find (no regex).
replace string Yes The replacement text; empty string deletes the occurrences.
tab_ids array — Limit the replacement to these tabs (from list_tabs); omit for all tabs.
match_case boolean — Case-sensitive matching (default true).
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.

Parameters from the server's own tool schema.

Why replace_all_text is rated Medium

An AI agent can call replace_all_text 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.

Risk signalsBulk/mass operation — affects multiple targets

Questions about replace_all_text

What does the replace_all_text tool do? +

Replaces EVERY occurrence of a literal string (no regex) across the whole document, or only in the tabs named by tab_ids. match_case defaults to true. Returns occurrencesChanged in the batchUpdate reply — 0 means the text was not found, not an error. Safer than replace_range for textual substitutions because it does not depend on indexes; use replace_range when position matters (e.g. only one of several occurrences). 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_all_text accept? +

replace_all_text accepts 5 parameters: find, replace, tab_ids, match_case, document_id. Required: find, replace, document_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on replace_all_text? +

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

What risk level is replace_all_text? +

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 replace_all_text? +

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

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Google Docs's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.