reject_change

Reject a single tracked change by its change_id.

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-change.md

WHAT IT DOES

What reject_change does on Docx

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

Rejecting a tracked change modifies the document by reverting a proposed edit, which is a reversible write operation. While it removes a change object, it does not permanently delete underlying document content—the original state is preserved and can be restored by accepting the change instead. This is write-level modification rather than destructive deletion.

From the tool's definition Tool name 'reject_change' and description 'Reject a single tracked change by its change_id' indicate modification of document state by rejecting (removing/reverting) a tracked change in a Word document.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reject_change Rate-limited

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

FAQ

Questions about reject_change

What does the reject_change tool do? +

Reject a single tracked change by its change_id. 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_change? +

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

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

Can I rate-limit reject_change? +

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

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

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