{"version":"2.1.317","anchor":"sandboxmcp-toolcheck-excludes-a-specific-module","canonical_anchor":"sandboxmcp-toolcheck-excludes-a-specific-module","heading":"Tool checks now leave out one more loaded module","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sandboxmcp-toolcheck-excludes-a-specific-module","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Tool checks now leave out one more loaded module\n\nWhen Claude Code checks a tool, it now leaves one particular module out of the modules it considers, under a certain condition\n\n**Unclear.** Which module is now left out, and when, is not clear.\n\n**What**\n\nWhen Claude Code checks a tool before using it, it filters the list of loaded modules it considers. A module is a piece of add-on code that has been loaded. That filter now leaves out one more specific module when a certain condition holds. Before, only the existing filter applied.\n\n**Why**\n\nThis is a small change to which modules are taken into account during tool checks.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}