Find and replace text in the document Parameters: - find_text: Text to find - replace_text: Text to replace with
AI agents use find_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.
This tool modifies document content by replacing text, which is a reversible write operation. While it could overwrite important content, the change is not inherently irreversible (documents can be restored or the replacement reversed), placing it in the Write category. Severity is medium because a broad find-and-replace could corrupt significant portions of a document if misused.
From the tool's definition Find and replace text in the document — modifies existing document content by substituting matched text with replacement text
Documented attack patterns abuse exactly the kind of access find_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 find_and_replace:
{
"version": "1",
"default": "deny",
"tools": {
"find_and_replace": {
"limits": [
{
"counter": "find_and_replace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} find_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.
Find and replace text in the document Parameters: - find_text: Text to find - replace_text: Text to replace with. 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 find_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.
find_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 find_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 find_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.
find_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.