{"version":"2.1.315","anchor":"device-mcp-serving-consent-events-de-duplicated","canonical_anchor":"device-mcp-serving-consent-events-de-duplicated","heading":"Device MCP consent prompts can come back after being put off","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/device-mcp-serving-consent-events-de-duplicated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Device MCP consent prompts can come back after being put off\n\nOn-device MCP serving now tracks its events in one place and sends a consent prompt again once it is no longer put off\n\n**What**\n\nClaude Code can serve MCP tools (add-on tools) from your device, and it asks for consent before doing so. The events this uses are now tracked in one place instead of two. When a \"consent not set\" event arrives after an earlier one was put off, and it is no longer put off, Claude Code clears the old put-off marker and sends the event again.\n\n**Why**\n\nThis stops consent prompts getting stuck after they have been put off once.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}