This record as markdown: /tools/securityronin-docx-mcp/compare-documents.md
What compare_documents does on Docx
AI agents invoke compare_documents to trigger actions in Docx. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why compare_documents is rated High
The tool name suggests comparing two documents. In the context of a Word document MCP server that supports track changes, document comparison typically generates a new document or inserts tracked changes (a write/execute operation). However, the description is empty, so confidence is low.
From the tool's definition Tool name: compare_documents; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs compare_documents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_documents, this is the rule to start with:
compare_documents stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every compare_documents call is checked against it from then on.
Questions about compare_documents
compare_documents is a execute tool on the Docx MCP server. It is categorised as a Execute tool in the Docx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docx MCP server in PolicyLayer and add a rule for compare_documents: 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.
compare_documents is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the compare_documents 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 compare_documents. 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.
compare_documents 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.
More on Docx, and thousands of servers like it.
This server
Across the catalogue