{"version":"2.1.323","anchor":"mcp-tool-classification-adds-linked-computer-category","canonical_anchor":"mcp-tool-classification-adds-linked-computer-category","heading":"New linked_computer tool category with a fail-closed fallback","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-tool-classification-adds-linked-computer-category","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### New linked_computer tool category with a fail-closed fallback\n\nMCP tools can now be classed as linked_computer, and if the restriction lookup fails for them, an enforced fallback applies instead of nothing\n\n**Unclear.** What Claude Code does with this category, such as whether it changes what a user sees or how these tools behave, is not stated.\n\n**What**\n\nClaude Code sorts MCP tools (tools added by add-on programs) into categories. There is now a `linked_computer` category, which applies to tools that act on a computer linked to the session.\n\n- Classifying MCP tools can now return `linked_computer` for tools that match a new check. Before, it returned only browser, computer_use, simulator or nothing. Browser detection was folded into one helper.\n\n- When the lookup that decides a restriction verdict fails with an error, Claude Code now checks a condition. If the condition holds, it returns an enforced verdict with `flagSource` \"fallback\" and family `linked_computer`. Before, it logged the error and returned no verdict.\n\n**Why**\n\nTools for linked computers are treated as their own group. If the lookup fails, the restriction stays in force for them rather than being dropped.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: yes"}