Cross-reference endnote IDs between document.xml and endnotes.xml.
AI agents call validate_endnotes 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.
This tool performs a read-only validation check by cross-referencing IDs between two XML components of a Word document. It retrieves and audits structural consistency without making changes, reversing changes, executing commands, deleting data, or handling financial operations. The low severity reflects minimal risk from misuse—a validation operation cannot corrupt document data or cause significant harm.
From the tool's definition Tool name 'validate_endnotes' and description 'Cross-reference endnote IDs between document.xml and endnotes.xml' indicates a verification/validation operation that queries and compares document structures without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access validate_endnotes 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_endnotes:
{
"version": "1",
"default": "deny",
"tools": {
"validate_endnotes": {}
}
}validate_endnotes 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 endnote IDs between document.xml and endnotes.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_endnotes: 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_endnotes 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_endnotes 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_endnotes. 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_endnotes 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.