{"version":"2.1.277","anchor":"device-mcp-consent-control-request-kind-defined-but-no-calle","canonical_anchor":"device-mcp-consent-control-request-kind-defined-but-no-calle","heading":"device_mcp_consent control-request kind defined but no caller found in this slice","tier":"soon","area":"Device Binding","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/device-mcp-consent-control-request-kind-defined-but-no-calle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### device_mcp_consent control-request kind defined but no caller found in this slice\n\nA new 'device_mcp_consent' message format was added for approving MCP server changes on a device, though nothing yet appears to trigger it\n\n**Unclear.** No caller of this new message format was found, so it's unclear when or whether it is currently shown to users.\n\n**What**\n\nA new internal message format called `device_mcp_consent` has been defined. It describes a consent prompt that would list MCP servers (Model Context Protocol servers, external tools Claude Code can connect to) that were changed or added on a device, with a default answer of \"not now\" if no response is given.\n\n**Why**\n\nThis appears to be groundwork for a future feature asking you to approve MCP server changes per device; no part of Claude Code currently triggers this prompt.\n\n- Area: Device Binding\n- Names: `device_mcp_consent`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}