get_endnotes
Get all endnotes with their ID and text content.
This record as markdown: /tools/securityronin-docx-mcp/get-endnotes.md
What get_endnotes does on Docx
AI agents call get_endnotes to retrieve information from Docx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_endnotes is rated Low
This tool retrieves and queries endnote data from a Word document without side effects. It performs a read-only operation consistent with the 'Read' category definition (retrieves or queries data; no side effects). The low severity reflects minimal risk even if misused by an AI agent, as it only exposes existing document content.
From the tool's definition Tool name 'get_endnotes' and description 'Get all endnotes with their ID and text content' explicitly indicate retrieval of existing document data with no modification, creation, or deletion.
Attacks that exploit this kind of access
The rule that runs get_endnotes 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 get_endnotes, this is the rule to start with:
get_endnotes is read-only, so it stays allowed. 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 get_endnotes call is checked against it from then on.
Questions about get_endnotes
Get all endnotes 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.
Register the Docx MCP server in PolicyLayer and add a rule for get_endnotes: 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.
get_endnotes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_endnotes 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 get_endnotes. 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.
get_endnotes 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