Cross-reference footnote IDs between document.xml and footnotes.xml.
AI agents call validate_footnotes 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 performs structural auditing and validation by checking consistency between XML components. It retrieves and examines data to verify footnote integrity but does not create, modify, delete, or execute external operations. This is a classic Read operation with minimal blast radius—misuse would only expose document structure information or report validation results.
From the tool's definition Tool description states 'Cross-reference footnote IDs between document.xml and footnotes.xml' — a validation/verification operation that queries and compares existing data without modifying it.
Documented attack patterns abuse exactly the kind of access validate_footnotes 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 validate_footnotes:
{
"version": "1",
"default": "deny",
"tools": {
"validate_footnotes": {}
}
}validate_footnotes 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.
Cross-reference footnote IDs between document.xml and footnotes.xml. 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 validate_footnotes: 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.
validate_footnotes 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 validate_footnotes 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 validate_footnotes. 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.
validate_footnotes 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.