{"version":"2.1.318","anchor":"tool-grant-check-for-the-primitive-tool-now-consults-primiti","canonical_anchor":"tool-grant-check-for-the-primitive-tool-now-consults-primiti","heading":"A restricted primitiveToolGrant can now remove a tool from the session","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/tool-grant-check-for-the-primitive-tool-now-consults-primiti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### A restricted `primitiveToolGrant` can now remove a tool from the session\n\nIf `primitiveToolGrant` is set and leaves out a certain tool, Claude Code no longer treats a related tool as available\n\n**Unclear.** It is not clear which tools this check covers.\n\n**What**\n\nThe `primitiveToolGrant` session option is now actually checked when Claude Code works out which tools a session has. When a mode check passes, the option is set, and it does not include one particular tool, a related tool is now treated as unavailable.\n\nBefore, that part of the check always passed, so the option had no effect there.\n\n**Why**\n\nIf you set `primitiveToolGrant` from your own code, a narrower grant now limits which tools Claude can use, where before it did not.\n\n- Area: SDK\n- Names: `primitiveToolGrant`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}