{"version":"2.1.267","anchor":"mcp-tool-passthrough-adoption-telemetry-and-policy-gating","canonical_anchor":"new-mcp-passthrough-tool-adoption-pipeline-behind-adoptmcpov","heading":"MCP tools can now be 'adopted' as passthrough tools instead of routed through the device bridge","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/mcp-tool-passthrough-adoption-telemetry-and-policy-gating","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### MCP tools can now be 'adopted' as passthrough tools instead of routed through the device bridge\n\nRemote worker sessions can now adopt a machine's MCP tools directly under policy, tracked via new passthrough_adopted\/declined telemetry\n\n**What**\n\n- A reworked remote-tools setup pipeline, gated by `adoptMcpOverChannelSwitchOn`, computes a `machineMcpToolsPolicy` (allowed\/denied\/pending\/unavailable) for each MCP server and decides whether its tools are \"adopted\" as passthrough tools, used directly by a remote worker, instead of being routed through the device bridge. Adoption requires remote tool forwarding to be enabled, the channel switch to be on, policy to allow it, and the tool not to be disabled.\n\n- The remote-tools announce handler now computes `passthrough_adopted` and `passthrough_declined` (with reasons `policy`, `pending`, or `unavailable`) outcomes and reports them in telemetry.\n\n- The `remote_tools_announce` acknowledgement schema was extended with `passthrough_adopted` (count of MCP tools kept) and `passthrough_declined` fields, and `ignored_tools` now documents more reasons, including tools beyond the cap that the worker keeps.\n\n**Why** Routing every MCP tool call through the device bridge adds overhead; letting a remote worker adopt and call MCP tools directly, when policy allows, should make those calls faster while keeping visibility into which tools were adopted versus declined and why.\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.267; this account: off, anonymous baseline: off, compiled default: off)\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}