New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

validate_footnotes

Cross-reference footnote IDs between document.xml and footnotes.xml.

SERVERDocx SOURCEsecurityronin/docx-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/validate-footnotes.md

What validate_footnotes does on Docx

AI agents call validate_footnotes to retrieve information from Docx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why validate_footnotes is rated Low

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.

Questions about validate_footnotes

What does the validate_footnotes tool do? +

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.

How do I enforce a policy on validate_footnotes? +

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.

What risk level is validate_footnotes? +

validate_footnotes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit validate_footnotes? +

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.

How do I block validate_footnotes completely? +

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.

What MCP server provides validate_footnotes? +

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.

More on Docx, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Docx's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.