You'll notice
Trying to call another machine's session-owned MCP tool locally now fails with a clear error instead of silently misbehaving
What
When 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.
Why
Previously 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.