{"version":"2.1.299","anchor":"evalworkflow-execution-disallowed-tools-merged-across-layer","canonical_anchor":"evalworkflow-execution-disallowed-tools-merged-across-layer","heading":"Blocked tool lists now add up across configuration layers","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/evalworkflow-execution-disallowed-tools-merged-across-layer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Blocked tool lists now add up across configuration layers\n\nLists of disallowed tools from a base configuration and an override are now combined, so the base list no longer gets dropped\n\n**What**\n\nWhen Claude Code builds the settings for running an eval or a workflow, the `disallowed_tools` list from the base configuration and the one from the override are now combined. Before, the override's list replaced the base list.\n\n**Why**\n\nTools blocked in a parent configuration stay blocked when an override adds its own list.\n\n- Area: Elsewhere\n- Names: `disallowed_tools`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}