{"version":"2.1.302","anchor":"bridge-mcp-server-permission-check-now-consults-session-urls","canonical_anchor":"bridge-mcp-server-permission-check-now-consults-session-urls","heading":"Bridge tools inside a session are allowed or denied based on session addresses","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/bridge-mcp-server-permission-check-now-consults-session-urls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Bridge tools inside a session are allowed or denied based on session addresses\n\nWhen no bridge server exists, Claude Code now answers allowed or denied for its tools by checking session addresses against the session's rules\n\n**Unclear.** The condition that makes the check answer denied straight away is not stated.\n\n**What**\n\nThe bridge is an MCP server that runs inside a Claude Code session and offers tools. Claude Code checks whether those tools may be used. That check now:\n\n- answers denied straight away when a certain condition is true\n\n- when no bridge server exists, checks session addresses beginning `cse_` and `session_` against the session's rules and answers denied or allowed\n\nBefore, when no bridge server existed, the answer was pending or unavailable.\n\n**Why**\n\nIt changes when the bridge's tools are available in a session.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}