{"version":"2.1.269","anchor":"auto-denial-telemetry-event-now-excludes-path-scoped-deny-ru","canonical_anchor":"auto-denial-telemetry-event-now-excludes-path-scoped-deny-ru","heading":"Auto-denial telemetry event now excludes path-scoped deny-rule refusals of file tools","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/auto-denial-telemetry-event-now-excludes-path-scoped-deny-ru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Auto-denial telemetry event now excludes path-scoped deny-rule refusals of file tools\n\nAuto-denial telemetry no longer counts Read\/Edit\/Write calls blocked by a path-scoped deny rule\n\n**What**\n\nClaude Code records a telemetry event when a tool call is automatically denied without ever showing you a permission prompt. The documentation for that event now spells out an additional case it does not cover: calls to the file tools (`Read`, `Edit`, `Write`) that get refused because of a path-scoped deny rule (a rule blocking access to a specific file path). This joins two exclusions already documented: denials from a `PreToolUse` hook, and denials overridden by a deny rule.\n\n**Why**\n\nThis matters mainly for anyone analyzing this telemetry event: it clarifies that path-scoped file denials won't show up there, so counts from this event undercount that particular category of automatic denial.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}