# 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:""}, 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":""}} 5. {"action":"decide","decision":"accept","target":{"kind":"ids","ids":["",""]}} 6. {"action":"decide","decision":"reject","target":{"kind":"range","range":{"kind":"text","segments":[{"blockId":"","range":{"start":0,"end":5}}]}}} 7. {"action":"decide","decision":"reject","target":{"scope":"all"}} Agent View of the PolicyLayer registry record for `superdoc_track_changes`. HTML page: https://policylayer.com/tools/superdoc-mcp/superdoc-track-changes ## Facts - Tool: `superdoc_track_changes` - Server: Superdoc (`@superdoc/mcp`) — https://policylayer.com/tools/superdoc-mcp.md - Install: `npx -y @superdoc/mcp` - Homepage: https://www.npmjs.com/package/@superdoc/mcp - Risk category: Destructive (Critical risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 11 (2 required) - Recommended policy verdict: Hidden ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `in` | object | no | 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 | no | Filter by change type. Canonical values: 'insertion', 'deletion', 'replacement', 'formatting', 'move', 'structural'. Legacy aliases 'insert', 'delete', and 'for | | `force` | boolean | no | Bypass confirmation checks. Only for action 'decide'. Omit for other actions. | | `limit` | integer | no | 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 | no | Number of tracked changes to skip for pagination. Only for action 'list'. Omit for other actions. | | `target` | object | no | Decision target. Canonical shapes: { kind: 'id', id, story? } (one whole logical tracked change), { kind: 'ids', ids } (several whole logical tracked changes in | | `decision` | string | no | Required for action 'decide'. | | `changeMode` | string | no | 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 | no | 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. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "superdoc_track_changes", "arguments": { "action": "", "session_id": "" } } } ``` ## 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 signals: High parameter count (11 properties) ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Superdoc: ```json { "version": "1", "default": "deny", "hide": [ "superdoc_track_changes" ] } ``` ## Other tools on Superdoc (12) - `superdoc_mutations` — Destructive — https://policylayer.com/tools/superdoc-mcp/superdoc-mutations.md - `superdoc_table` — Destructive — https://policylayer.com/tools/superdoc-mcp/superdoc-table.md - `superdoc_format` — Execute — https://policylayer.com/tools/superdoc-mcp/superdoc-format.md - `superdoc_get_content` — Read — https://policylayer.com/tools/superdoc-mcp/superdoc-get-content.md - `superdoc_list` — Read — https://policylayer.com/tools/superdoc-mcp/superdoc-list.md - `superdoc_search` — Read — https://policylayer.com/tools/superdoc-mcp/superdoc-search.md - `superdoc_close` — Write — https://policylayer.com/tools/superdoc-mcp/superdoc-close.md - `superdoc_comment` — Write — https://policylayer.com/tools/superdoc-mcp/superdoc-comment.md - `superdoc_create` — Write — https://policylayer.com/tools/superdoc-mcp/superdoc-create.md - `superdoc_edit` — Write — https://policylayer.com/tools/superdoc-mcp/superdoc-edit.md - `superdoc_open` — Write — https://policylayer.com/tools/superdoc-mcp/superdoc-open.md - `superdoc_save` — Write — https://policylayer.com/tools/superdoc-mcp/superdoc-save.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=superdoc-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/superdoc-mcp