Clause-aware diff between the open contract and another .docx file.
AI agents call compare_contracts to retrieve information from Docx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool compares two documents and returns differences. A diff operation reads both files and reports discrepancies without modifying either document. No write, execute, or destructive actions are implied.
From the tool's definition 'diff between the open contract and another .docx file' — performs a comparison/diff operation, which is a read/query action with no side effects
Documented attack patterns abuse exactly the kind of access compare_contracts 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 compare_contracts:
{
"version": "1",
"default": "deny",
"tools": {
"compare_contracts": {}
}
}compare_contracts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Clause-aware diff between the open contract and another .docx file. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.
Register the Docx MCP server in PolicyLayer and add a rule for compare_contracts: 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_contracts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the compare_contracts 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_contracts. 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_contracts 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.