{"version":"2.1.318","anchor":"disallowed-tools-warning-for-claudeai-connector-wildcards","canonical_anchor":"disallowed-tools-warning-for-claudeai-connector-wildcards","heading":"--disallowed-tools check drops its warning about claude.ai connector wildcards","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/disallowed-tools-warning-for-claudeai-connector-wildcards","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### `--disallowed-tools` check drops its warning about claude.ai connector wildcards\n\nClaude Code no longer warns that a `*` in a claude.ai connector name in `--disallowed-tools` blocks nothing in a cloud session\n\n**Unclear.** Whether this warning now appears somewhere else is not known.\n\n**What**\n\n`--disallowed-tools` lists the tools Claude is not allowed to use. A claude.ai connector is a tool connection you set up on claude.ai. A cloud session is one that runs in the cloud rather than on your computer.\n\nClaude Code used to warn that a `*` in a claude.ai connector's name blocks no connector in a cloud session. This check no longer gives that warning. It now only lists your rules, shortened with \"and N more\" when there are many.\n\n**Why**\n\nIf you rely on a `*` in a connector name to block connectors in cloud sessions, that rule still blocks none of them, and you may no longer be told so.\n\n- Area: Permissions\n- Names: `--disallowed-tools`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}