{"version":"2.1.269","anchor":"background-memory-pass-can-call-a-restricted-tool-set-via","canonical_anchor":"background-memory-pass-can-call-a-restricted-tool-set-via","heading":"Background 'memory pass' can call a restricted tool set via CCR memory server","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/background-memory-pass-can-call-a-restricted-tool-set-via","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Background 'memory pass' can call a restricted tool set via CCR memory server\n\nA background 'memory pass' can now call a restricted set of tools, but only through a CCR memory server and under strict conditions\n\n**What**\n\nA new function builds a permission-check for a background task referred to as 'this background memory pass'. It only allows a tool call to proceed if all of the following hold:\n\n- a CCR memory MCP server is mounted for the session\n\n- the tool isn't blocked by an existing session permission rule\n\n- the tool's name appears in an allow-list\n\n- for tools that can write, the current conversation turn hasn't already moved on\n\nIf no CCR memory server is present, the background memory pass is blocked entirely.\n\n**Why**\n\nThis lets a background process manage memory-related work using a small, controlled set of tools without opening up broader tool access, and prevents write operations from landing after the relevant turn has already ended.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}