{"version":"2.1.315","anchor":"mcp-client-hosted-server-permission-policy-notice","canonical_anchor":"mcp-client-hosted-server-permission-policy-notice","heading":"New notice when MCP permission rules do not apply to a client-hosted server","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-client-hosted-server-permission-policy-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### New notice when MCP permission rules do not apply to a client-hosted server\n\nClaude Code now warns when a client-hosted MCP server's permission_policy is not applied, so always_ask and always_deny have no effect\n\n**Unclear.** Which kinds of session show this notice is not stated.\n\n**What**\n\nAn MCP server is an add-on that gives Claude extra tools, and a client-hosted one is run by the program Claude Code is connected to. Claude Code now shows a notice when a session does not apply a client-hosted MCP server's per-tool `permission_policy`. The notice says that no `always_ask` or `always_deny` rule in that entry takes effect, and that the server is otherwise unchanged. It joins an existing set of similar notices.\n\n**Why**\n\nRules meant to ask before a tool runs, or to block it, are not enforced for these servers in such sessions. The notice makes that visible instead of leaving it silent.\n\n- Area: MCP\n- Names: `permission_policy`, `always_ask`, `always_deny`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}