You'll notice
Calling a remote session's own MCP tools directly now fails with a clear error instead of misrouting
What
When 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.
Why
This 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.