Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.166 Home All releases olderv2.1.165 v2.1.167newer

Wildcard allow-rule validation now rejects unsafe patterns

Allow rules with unscoped wildcards (e.g. mcp__*) are now rejected at parse time with a clear error:

> Wildcard tool name "mcp__" is not supported in allow rules. An allow pattern must name the scope it widens — globs are permitted only in the tool position after a literal mcp__<server>__ prefix. Deny and ask rules accept wildcards anywhere. Examples: mcp__puppeteer__

Deny 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.

Evidence

New wildcard allow-rule validator (search for "is not supported in allow rules")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.166 →