Claude now tracks whether your allowed-MCP-server rules could actually be evaluated.
What's wrong with this entry?
Matching a server against allowedMcpServers now reports, once per session, whether the predicate could be evaluated.
- A successful match reports "ok".
- Unresolved variables in a policy command or URL report "missing_policy_var".
- An unsafe URL expansion reports "unsafe_expansion".
- All reported under the metric name mcp_policy_predicate.
mcp_policy_predicate
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
MCP allow/deny rules compare expanded env-var values
Both mention allowed server
-
v2.1.248
MCP server allow and deny lists get settings keys
Both mention allowed server
-
v2.1.219
MCP policy allow/deny entries now expand
${VAR}environment references, and unsafe URL expansions fail closedBoth mention allowed server