This record as markdown: /tools/securityronin-docx-mcp/update-endnote.md
What update_endnote does on Docx
AI agents use update_endnote 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.
Why update_endnote is rated Medium
This tool modifies existing endnote content within a Word document. While the change is reversible (via undo or by updating again), it alters document content. It does not execute code, delete irreversibly, involve financial transactions, or read without side effects. The severity is medium because misuse could corrupt or alter document meaning, but the impact is limited to endnote text within a single document.
From the tool's definition Tool name 'update_endnote' and description 'Update the text of an existing endnote' indicate modification of document content. The verb 'update' and the operation of changing endnote text are characteristic of Write operations.
Attacks that exploit this kind of access
The rule that runs update_endnote 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_endnote, this is the rule to start with:
update_endnote 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every update_endnote call is checked against it from then on.
Questions about update_endnote
Update the text of an existing endnote. 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.
Register the Docx MCP server in PolicyLayer and add a rule for update_endnote: 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.
update_endnote is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_endnote 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 update_endnote. 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.
update_endnote 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.
This server
Across the catalogue