generate_toc
Generate a Table of Contents from document headings.
This record as markdown: /tools/securityronin-docx-mcp/generate-toc.md
What generate_toc does on Docx
AI agents use generate_toc 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 generate_toc is rated Medium
Generating a TOC is a write operation—it creates or modifies document content by inserting a table of contents based on headings. This is reversible (can be deleted or regenerated), so it does not qualify as Destructive. It does not execute code, query external systems, move money, or have read-only semantics, so Execute, Financial, and Read are not applicable.
From the tool's definition The tool 'generate_toc' generates a Table of Contents, which creates new content (a TOC structure) in the document.
Attacks that exploit this kind of access
The rule that runs generate_toc 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 generate_toc, this is the rule to start with:
generate_toc 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 generate_toc call is checked against it from then on.
Questions about generate_toc
Generate a Table of Contents from document headings. 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 generate_toc: 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.
generate_toc 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 generate_toc 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 generate_toc. 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.
generate_toc 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