Merge tracked changes from N reviewer copies into the open document.
AI agents use merge_review_rounds to create or update resources in Docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.
This tool modifies an open document by merging tracked changes from multiple sources. While reversible (changes can be undone via undo/rejection mechanisms typical in document editors), it represents a write operation that transforms document state. It does not delete data irreversibly, so Destructive does not apply. The operation is a create/modify action rather than read-only or code execution.
From the tool's definition Tool name 'merge_review_rounds' and description 'Merge tracked changes from N reviewer copies into the open document' — this performs a modification operation that integrates external changes into the document, materially altering its content.
Documented attack patterns abuse exactly the kind of access merge_review_rounds gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for merge_review_rounds:
{
"version": "1",
"default": "deny",
"tools": {
"merge_review_rounds": {
"limits": [
{
"counter": "merge_review_rounds_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_review_rounds 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.
Merge tracked changes from N reviewer copies into the open document. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx MCP server in PolicyLayer and add a rule for merge_review_rounds: 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 Docx. Nothing to install.
merge_review_rounds 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 merge_review_rounds 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 merge_review_rounds. 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.
merge_review_rounds is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 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.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.