add_footnote_ref

A write tool on the Docx MCP server.

SERVERDocx SOURCEsecurityronin/docx-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/add-footnote-ref.md

WHAT IT DOES

What add_footnote_ref does on Docx

AI agents use add_footnote_ref to create or update resources in Docx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.

RISK

Why add_footnote_ref is rated Medium

This tool creates/modifies document content by inserting a footnote reference, which is a reversible Write operation. It does not execute arbitrary code, delete data, or cause financial effects. The tool description is empty, slightly lowering confidence, but the pattern from sibling tools and server purpose clearly indicate Write semantics.

From the tool's definition Tool name 'add_footnote_ref' indicates it adds a footnote reference to a document. Sibling tools on the server include 'add_comment', 'add_equation', 'add_endnote', 'add_cross_reference', and 'add_bookmark'—all Write operations that create or modify document…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_footnote_ref safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_footnote_ref, this is the rule to start with:

add_footnote_ref Rate-limited

add_footnote_ref stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_footnote_ref": {
      "limits": [
        {
          "counter": "add_footnote_ref_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every add_footnote_ref call is checked against it from then on.

FAQ

Questions about add_footnote_ref

What does the add_footnote_ref tool do? +

add_footnote_ref is a write tool on the Docx MCP server. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_footnote_ref? +

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

add_footnote_ref is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_footnote_ref? +

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

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

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

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →