suppress_numbering
Remove list numbering from a paragraph by setting numId to 0.
This record as markdown: /tools/securityronin-docx-mcp/suppress-numbering.md
What suppress_numbering does on Docx
AI agents use suppress_numbering 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 suppress_numbering is rated Medium
This tool modifies document structure by removing list numbering from a paragraph. It is a reversible write operation (numbering can be restored), making it a Write category action. Misuse could alter document formatting in unintended ways, warranting medium severity.
From the tool's definition Remove list numbering from a paragraph by setting numId to 0
Attacks that exploit this kind of access
The rule that runs suppress_numbering 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 suppress_numbering, this is the rule to start with:
suppress_numbering 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 suppress_numbering call is checked against it from then on.
Questions about suppress_numbering
Remove list numbering from a paragraph by setting numId to 0. 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 suppress_numbering: 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.
suppress_numbering 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 suppress_numbering 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 suppress_numbering. 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.
suppress_numbering 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