What
A new compliance/federation enforcement mechanism was added:
- New helper functions implement checks around "compliance_taints" and restriction keys prefixed
enforce_/require_, plus a newANTHROPIC_FEDERATION_RULE_IDenvironment variable used to build a federation cache key. - The feature-gate check that runs when a cached permission value is missing was reworked to first consult a new set of session-local "hinted" denials and compliance taints before remote config has even loaded, gated behind an internal check that requires first-party Anthropic authentication.
Why
This lets organization-enforced compliance restrictions apply immediately, even before the remote configuration that normally carries them has finished loading, closing a gap where early actions could bypass a restriction.
Names in the bundleANTHROPIC_FEDERATION_RULE_IDANTHROPIC_ORGANIZATION_ID
Documented inapi/agents-and-tools/mcp-tunnels/deploy-compose
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up ANTHROPIC_ORGANIZATION_ID, on Authentication.
| Federation variables | `ANTHROPIC_FEDERATION_RULE_ID` and `ANTHROPIC_ORGANIZATION_ID`, both set | Above |authentication see the edit
Confirmed since
Anthropic's documentation has since written up ANTHROPIC_FEDERATION_RULE_ID, on Authentication.
| Federation variables | `ANTHROPIC_FEDERATION_RULE_ID` and `ANTHROPIC_ORGANIZATION_ID`, both set | Above |authentication see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up ANTHROPIC_FEDERATION_RULE_ID, on Authentication.