accept_change

Accept 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/accept-change.md

WHAT IT DOES

What accept_change does on Docx

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

This tool modifies document content by accepting tracked changes, which alters the document's revision history and final content state. While reversible (an accepted change could theoretically be rejected), it is a Write operation that commits a document modification. It is not Destructive because the original change data is preserved in the document's revision history and the action can be undone.

From the tool's definition Tool name 'accept_change' and description 'Accept a single tracked change' indicates modification of document state. The server description confirms it handles 'track changes' and 'editing' capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

accept_change Rate-limited

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

FAQ

Questions about accept_change

What does the accept_change tool do? +

Accept 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 accept_change? +

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

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

Can I rate-limit accept_change? +

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

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

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