superdoc_track_changes
Review and resolve tracked changes (insertions, deletions, replacements, format changes) in the document. Action "list" returns all tracked changes with optional filtering by type (insert, delete, replacement, format) and pagination (limit, offset). Each change includes an ID, type, author, times...
This record as markdown: /tools/superdoc-mcp/superdoc-track-changes.md
What superdoc_track_changes does on Superdoc
AI agents call superdoc_track_changes to permanently remove resources in Superdoc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
in | object | — | Story scope. Omit for body only, pass a StoryLocator for a single story, or 'all' for body + every revision-capable non-body story. Only for action 'list'. Omit |
type | string | — | Filter by change type. Canonical values: 'insertion', 'deletion', 'replacement', 'formatting', 'move', 'structural'. Legacy aliases 'insert', 'delete', and 'for |
force | boolean | — | Bypass confirmation checks. Only for action 'decide'. Omit for other actions. |
limit | integer | — | Maximum number of tracked changes to return. Only for action 'list'. Omit for other actions. |
action | string | Yes | The action to perform. One of: decide, list. |
offset | integer | — | Number of tracked changes to skip for pagination. Only for action 'list'. Omit for other actions. |
target | object | — | Decision target. Canonical shapes: { kind: 'id', id, story? } (one whole logical tracked change), { kind: 'ids', ids } (several whole logical tracked changes in |
decision | string | — | Required for action 'decide'. |
changeMode | string | — | Edit mode: "direct" applies changes immediately, "tracked" records as suggestions. Only for action 'decide'. Omit for other actions. |
session_id | string | Yes | Session ID from superdoc_open. |
expectedRevision | string | — | Backward-compatible alias for options.expectedRevision. Explicit mutation options take precedence when both are supplied. Only for action 'decide'. Omit for oth |
Parameters from the server's own tool schema.
Why superdoc_track_changes is rated Critical
An AI agent that decides to call superdoc_track_changes doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Superdoc is gone. There is no undo for destructive operations.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs superdoc_track_changes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Superdoc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For superdoc_track_changes, this is the rule to start with:
superdoc_track_changes is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Superdoc, apply this rule, and every superdoc_track_changes call is checked against it from then on.
Questions about superdoc_track_changes
Review and resolve tracked changes (insertions, deletions, replacements, format changes) in the document. Action "list" returns all tracked changes with optional filtering by type (insert, delete, replacement, format) and pagination (limit, offset). Each change includes an ID, type, author, timestamp, and content preview. Action "decide" accepts or rejects changes. Pass decision:"accept" to apply the change permanently, or decision:"reject" to discard it. Target a single change with {id:"<changeId>"}, several whole changes atomically with {kind:"ids", ids:[...]}, a partial selection with {kind:"range", range:{...}}, or all changes at once with {scope:"all"} (optionally plus story). Do NOT use this tool unless the document has tracked changes. Use superdoc_get_content info to check the tracked change count first. EXAMPLES: 1. {"action":"list"} 2. {"action":"list","type":"insertion","limit":10} 3. {"action":"list","type":"replacement","limit":10} 4. {"action":"decide","decision":"accept","target":{"id":"<changeId>"}} 5. {"action":"decide","decision":"accept","target":{"kind":"ids","ids":["<changeId1>","<changeId2>"]}} 6. {"action":"decide","decision":"reject","target":{"kind":"range","range":{"kind":"text","segments":[{"blockId":"<blockId>","range":{"start":0,"end":5}}]}}} 7. {"action":"decide","decision":"reject","target":{"scope":"all"}}. It is categorised as a Destructive tool in the Superdoc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
superdoc_track_changes accepts 11 parameters: in, type, force, limit, action, offset, target, decision, changeMode, session_id, expectedRevision. Required: action, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Superdoc MCP server in PolicyLayer and add a rule for superdoc_track_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 Superdoc. Nothing to install.
superdoc_track_changes is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the superdoc_track_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.
Set action: deny in the PolicyLayer policy for superdoc_track_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.
superdoc_track_changes is provided by the Superdoc MCP server (@superdoc/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Superdoc, and thousands of servers like it.
Across the catalogue