Low Risk

get_footnotes

List all footnotes with their ID and text content.

How to control get_footnotes ↓

What get_footnotes does on Docx

AI agents call get_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.

Low Risk

Why get_footnotes needs a policy

The tool performs a read-only query of footnote metadata and content from a Word document. There are no side effects, no code execution, no data modification, and no destructive operations. The blast radius of misuse is minimal—an AI agent could only extract information that already exists in the document, with no capability to alter document state or trigger external actions.

From the tool's definition Tool name and description: 'List all footnotes with their ID and text content.' This is a retrieval operation that queries existing footnotes without modifying, executing, or deleting any document data.

Documented attack patterns abuse exactly the kind of access get_footnotes gives an agent:

How to control get_footnotes

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 get_footnotes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_footnotes": {}
  }
}

get_footnotes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Docx — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_footnotes

What does the get_footnotes tool do? +

List all footnotes with their ID and text content. 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 get_footnotes? +

Register the Docx MCP server in PolicyLayer and add a rule for get_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 get_footnotes? +

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

Can I rate-limit get_footnotes? +

Yes. Add a rate_limit block to the get_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 get_footnotes completely? +

Set action: deny in the PolicyLayer policy for get_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 get_footnotes? +

get_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.

Enforce policy on every Docx tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.