update_footnote

Update the text of an existing footnote.

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/update-footnote.md

WHAT IT DOES

What update_footnote does on Docx

AI agents use update_footnote 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 update_footnote is rated Medium

This tool modifies existing document data (footnote text) in a reversible manner, fitting the Write category definition of creating or modifying data reversibly. The blast radius is medium because unintended footnote modifications could alter document meaning and require manual review/correction, but the change is not irreversible.

From the tool's definition Tool name 'update_footnote' and description 'Update the text of an existing footnote' indicate modification of document content. The operation is reversible—the previous footnote text can be restored—distinguishing it from destructive deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_footnote 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 update_footnote, this is the rule to start with:

update_footnote Rate-limited

update_footnote 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": {
    "update_footnote": {
      "limits": [
        {
          "counter": "update_footnote_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 update_footnote call is checked against it from then on.

FAQ

Questions about update_footnote

What does the update_footnote tool do? +

Update the text of an existing footnote. 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 update_footnote? +

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

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

Can I rate-limit update_footnote? +

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

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

update_footnote 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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