{"version":"2.1.290","anchor":"tool-call-caller-declares-tool-host-interface-consent-refus","canonical_anchor":"tool-call-caller-declares-tool-host-interface-consent-refus","heading":"Consent refusal now covers MCP information tools","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/tool-call-caller-declares-tool-host-interface-consent-refus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Consent refusal now covers MCP information tools\n\nTool calls now name the tool host interface, and the refusal for tools that do not accept consent covers MCP information tools\n\n**What**\n\nWhen Claude Code serves a tool call, the information about who made the call now includes a `tool_host_interface` field.\n\nThe refusal given when a tool does not accept `consent` now also covers tools that report information about MCP servers. MCP servers are add-ons that give Claude extra tools. The message now says the tool does not accept it \"in this session\" instead of \"in a Projects session\".\n\n**Why**\n\nThe way plugin tool calls are passed between Claude Code and the app it runs in has changed. Anything that reads those calls or matches on the old refusal wording may see different text.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}