bates_number

A write tool on the Docx MCP server.

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/bates-number.md

WHAT IT DOES

What bates_number does on Docx

AI agents use bates_number 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 bates_number is rated Medium

Bates numbering adds sequential numbers/marks to document pages — a Write operation that modifies the document structure but does not delete data or execute arbitrary code. The lack of a description reduces confidence slightly, but the pattern of sibling tools and the nature of Bates numbering as a document annotation feature clearly indicates Write category.

From the tool's definition Tool name 'bates_number' suggests adding Bates numbering (sequential pagination/marking applied to documents, commonly used in legal document management).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bates_number Rate-limited

bates_number 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": {
    "bates_number": {
      "limits": [
        {
          "counter": "bates_number_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 bates_number call is checked against it from then on.

FAQ

Questions about bates_number

What does the bates_number tool do? +

bates_number is a write tool on the Docx MCP server. 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 bates_number? +

Register the Docx MCP server in PolicyLayer and add a rule for bates_number: 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 bates_number? +

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

Can I rate-limit bates_number? +

Yes. Add a rate_limit block to the bates_number 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 bates_number completely? +

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

bates_number 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 →