restart_numbering

Restart list numbering at a paragraph. Adds lvlOverride with startOverride.

SERVERDocx SOURCEsecurityronin/docx-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/restart-numbering.md

WHAT IT DOES

What restart_numbering does on Docx

AI agents use restart_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.

RISK

Why restart_numbering is rated Medium

This tool modifies the document by adding numbering override metadata (lvlOverride/startOverride) to a paragraph. It changes list numbering in a reversible way — it does not delete data or execute code, making Write the appropriate category. Misuse could corrupt document structure but is generally recoverable.

From the tool's definition Restart list numbering at a paragraph. Adds lvlOverride with startOverride.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs restart_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 restart_numbering, this is the rule to start with:

restart_numbering Rate-limited

restart_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restart_numbering": {
      "limits": [
        {
          "counter": "restart_numbering_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every restart_numbering call is checked against it from then on.

FAQ

Questions about restart_numbering

What does the restart_numbering tool do? +

Restart list numbering at a paragraph. Adds lvlOverride with startOverride. 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.

How do I enforce a policy on restart_numbering? +

Register the Docx MCP server in PolicyLayer and add a rule for restart_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.

What risk level is restart_numbering? +

restart_numbering is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit restart_numbering? +

Yes. Add a rate_limit block to the restart_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.

How do I block restart_numbering completely? +

Set action: deny in the PolicyLayer policy for restart_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.

What MCP server provides restart_numbering? +

restart_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.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →