reject_all_changes

Reject all tracked changes in document order.

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/reject-all-changes.md

WHAT IT DOES

What reject_all_changes does on Docx

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

This tool modifies a Word document by rejecting tracked changes, which is a reversible write operation. It does not permanently delete data (making it not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial).

From the tool's definition 'reject_all_changes' rejects tracked changes in a Word document. The description states it operates on 'tracked changes,' which are reversible modifications to document state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reject_all_changes Rate-limited

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

FAQ

Questions about reject_all_changes

What does the reject_all_changes tool do? +

Reject all tracked changes in document order. 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 reject_all_changes? +

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

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

Can I rate-limit reject_all_changes? +

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

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

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