{"version":"2.1.267","anchor":"new-mcp-tool-wrapper-explicitly-refuses-cross-machine-sessio","canonical_anchor":"new-mcp-tool-wrapper-explicitly-refuses-cross-machine-sessio","heading":"New MCP tool wrapper explicitly refuses cross-machine session-channel tools","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-mcp-tool-wrapper-explicitly-refuses-cross-machine-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New MCP tool wrapper explicitly refuses cross-machine session-channel tools\n\nTrying to call another machine's session-owned MCP tool locally now fails with a clear error instead of silently misbehaving\n\n**What**\n\nWhen multiple machines are connected in a shared session and one machine owns a particular MCP tool (a tool exposed by a Model Context Protocol server), a new wrapper now catches attempts to run that tool from a different machine and throws a clear error explaining that the tool belongs to that other session and can't run locally.\n\n**Why**\n\nPreviously such a call could fail silently or behave unpredictably; now the failure is explicit, making it obvious what went wrong instead of leaving the cause a mystery.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}