{"version":"2.1.309","anchor":"mcp-tool-allow-suggestion-may-target-the-session-instead-o","canonical_anchor":"mcp-tool-allow-suggestion-may-target-the-session-instead-o","heading":"An 'always allow' for one MCP server may last only for the session","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/mcp-tool-allow-suggestion-may-target-the-session-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### An 'always allow' for one MCP server may last only for the session\n\nFor one particular MCP server, the suggested 'always allow' rule can now apply to the current session instead of being saved to local settings\n\n**Unclear.** Which MCP server this applies to, and under what condition, is not known.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. When Claude Code asks permission to use an MCP tool, it suggests an allow rule you can accept. That rule was always saved to your local settings, so it lasted beyond the current session.\n\nFor one particular server, under a further condition, the suggested rule now applies to the current session only and is not saved. For every other server it is still saved to local settings.\n\n**Why**\n\nAn approval you give that server may need to be given again in your next session.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}