{"version":"2.1.268","anchor":"policy-limits-fetch-telemetry-now-reports-restrictioncompli","canonical_anchor":"policy-limits-fetch-telemetry-now-reports-restrictioncompli","heading":"Policy limits fetch telemetry now reports restriction\/compliance-taint counts","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/policy-limits-fetch-telemetry-now-reports-restrictioncompli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Policy limits fetch telemetry now reports restriction\/compliance-taint counts\n\nPolicy limits telemetry now counts denied restrictions and compliance-taint occurrences\n\n**What**\n\nThe `tengu_policy_limits_fetch` telemetry event, which fires when Claude Code fetches policy limits, now also records `restrictions_denied_count` (how many restrictions in the fetched policy were marked as not allowed) and `compliance_taint_count`.\n\n**Why**\n\nThis gives Anthropic more visibility into how restrictive an account's fetched policy is and how often compliance-taint conditions occur, building on earlier additions to this same telemetry event that recorded authentication details and server error information.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}