AI agents use replace_text_in_docx to create or update resources in MCP Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Tools environment.
This tool modifies document content by replacing text, which is a reversible write operation. It does not delete data irreversibly (would be Destructive) nor execute arbitrary code (would be Execute). The severity is medium because unintended text replacement could corrupt important documents, but changes can typically be undone via undo functions or version recovery.
From the tool's definition Tool name 'replace_text_in_docx' and description indicating text replacement functionality in Word documents. The verb 'replace' indicates modification of existing data.
Attacks that exploit this kind of access
替换Word文档中的文本. It is categorised as a Write tool in the MCP Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Tools MCP server in PolicyLayer and add a rule for replace_text_in_docx: 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 Tools. Nothing to install.
replace_text_in_docx 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 replace_text_in_docx 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 replace_text_in_docx. 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.
replace_text_in_docx is provided by the MCP Tools MCP server (starzzzzzzzzzzzzzz/mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →