{"version":"2.1.267","anchor":"session-channel-mcp-tools-now-stub-error-instead-of-silently","canonical_anchor":"session-channel-mcp-tools-now-stub-error-instead-of-silently","heading":"Session-channel MCP tools now stub-error instead of silently misrouting","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/session-channel-mcp-tools-now-stub-error-instead-of-silently","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Session-channel MCP tools now stub-error instead of silently misrouting\n\nCalling a remote session's own MCP tools directly now fails with a clear error instead of misrouting\n\n**What**\n\nWhen working in a remote session, tools that belong to that session's own MCP servers (external tool connections tied to a specific machine) are now represented by a placeholder. If something tries to call one of these tools directly instead of properly routing the call to the right machine, it now throws a specific error instead of silently running incorrectly on the wrong machine.\n\n**Why**\n\nThis turns a silent misrouting problem into a clear, catchable error, making it easier to notice and fix cases where a remote session's tools were being called the wrong way.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}