Search and replace text in the document, providing detailed replacement information and preview options Parameters: - keyword: Keyword to search for - replace_with: Text to replace with - preview_only: Whether to only preview without actually replacing, default is False
AI agents use search_and_replace to create or update resources in Doc/docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc/docx environment.
By default this tool performs actual text replacement across the document (preview_only=False), which is a reversible write operation. However, the blast radius is high because a poorly specified keyword could match and overwrite many occurrences throughout the document. It does not irreversibly delete data (original content could be restored), so Write is the appropriate category rather than Destructive.
From the tool's definition Search and replace text in the document...Whether to only preview without actually replacing, default is False
Documented attack patterns abuse exactly the kind of access search_and_replace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc/docx, and nothing reaches the server without passing your rules. This is the rule we recommend for search_and_replace:
{
"version": "1",
"default": "deny",
"tools": {
"search_and_replace": {
"limits": [
{
"counter": "search_and_replace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}search_and_replace 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.
Free to start. No card required.
Search and replace text in the document, providing detailed replacement information and preview options Parameters: - keyword: Keyword to search for - replace_with: Text to replace with - preview_only: Whether to only preview without actually replacing, default is False. It is categorised as a Write tool in the Doc/docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doc/docx MCP server in PolicyLayer and add a rule for search_and_replace: 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 Doc/docx. Nothing to install.
search_and_replace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the search_and_replace 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.
Set action: deny in the PolicyLayer policy for search_and_replace. 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.
search_and_replace is provided by the Doc/docx MCP server (meterlong/mcp-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Doc/docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Doc/docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.