Update the text of an existing endnote.
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.
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.
Documented attack patterns abuse exactly the kind of access update_endnote gives an agent:
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 update_endnote:
{
"version": "1",
"default": "deny",
"tools": {
"update_endnote": {
"limits": [
{
"counter": "update_endnote_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.