{"version":"2.1.310","anchor":"appifact-sdk-js-repl-permission-rule-check-shared-across-t","canonical_anchor":"appifact-sdk-js-repl-permission-rule-check-shared-across-t","heading":"A deny or ask rule for one code-running tool can now also apply to a second tool","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/appifact-sdk-js-repl-permission-rule-check-shared-across-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### A deny or ask rule for one code-running tool can now also apply to a second tool\n\nPermission rules that deny or ask before the artifact REPL tool runs code now also match a second tool name\n\n**Unclear.** The second tool name the rules now cover is not stated.\n\n**What**\n\nPermission rules let you deny a tool or require Claude Code to ask you before it runs. The check that applies these rules to a REPL tool, one that runs code for artifacts, now matches a list of two tool names instead of just that one. A deny or ask rule on one of the two names can now take effect for the other, with a message saying the tool runs code the same way and a rule denies or asks before it.\n\n**Why**\n\nIf you have rules for code-running tools, they may now block or prompt for a tool they did not cover before.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}