Enterprise AI Measurement Guide
AI Governance · Policy Enforcement
Blocked Events
How many times have engineers been blocked from using an AI tool by policy enforcement, and are those blocks generating the right friction or creating unnecessary obstacles?
What it shows
Blocked Events counts the number of times Larridin's policy enforcement layer prevented a user from accessing an AI tool during the selected period. Each blocked event represents an attempt to use a tool that the organization has set to "block" in its AI Tool Access Policy, the hard enforcement action that prevents access entirely.
Why it matters
Blocked events are the most visible governance signal. They create friction engineers feel immediately. A rising blocked event count can mean the policy is working (catching more unauthorized attempts) or that it is misconfigured (blocking tools that should be approved). The count by itself is not enough. The right question is which tools are generating the blocks and whether the volume is consistent with what the policy is supposed to be doing. Read it alongside Warned Events.
The Larridin angle
Larridin's Policy Enforcement layer distinguishes between blocks and warnings at the event level, so organizations can run a warn-first policy for newly flagged tools while maintaining hard blocks for tools with known data exposure risk. That distinction is invisible in governance frameworks that treat all enforcement as binary.