Accept a single tracked change by its change_id.
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.
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.
Documented attack patterns abuse exactly the kind of access accept_change gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for accept_change:
{
"version": "1",
"default": "deny",
"tools": {
"accept_change": {
"limits": [
{
"counter": "accept_change_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
accept_change is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.