{"version":"2.1.166","anchor":"wildcard-allow-rule-validation-now-rejects-unsafe-patterns","canonical_anchor":"wildcard-allow-rule-validation-now-rejects-unsafe-patterns","heading":"Wildcard allow-rule validation now rejects unsafe patterns","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.166\/e\/wildcard-allow-rule-validation-now-rejects-unsafe-patterns","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.166","markdown":"### Wildcard allow-rule validation now rejects unsafe patterns\n\nAllow rules with unscoped wildcards (e.g. `mcp__*`) are now rejected at parse time with a clear error:\n\n> Wildcard tool name \"mcp__*\" is not supported in allow rules. An allow pattern must name the scope it widens \u2014 globs are permitted only in the tool position after a literal mcp__<server>__ prefix. Deny and ask rules accept wildcards anywhere. Examples: mcp__puppeteer__*\n\nDeny and ask rules continue to accept wildcards anywhere. The validation fires at settings load so the error surfaces early rather than silently failing at permission-check time.\n\n**Evidence**\n\nNew wildcard allow-rule validator (search for `\"is not supported in allow rules\"`)"}