What Runtime Policy Coverage Means
Runtime policy coverage describes the proportion of an AI agent's real, in-execution behavior that passes through an active enforcement point before being allowed to proceed. This includes tool calls, data reads and writes, and any actions directed at other agents or systems. Coverage is a runtime property: it can only be measured by observing what an agent actually attempts to do, not by reading what a policy document says the agent is permitted to do.
Why the Static-Runtime Distinction Matters
A policy written into a configuration file or a governance standard is not the same as a policy that is checked at the moment an action is attempted. Static policy describes intent; runtime enforcement determines outcome. Because agent behavior is generated dynamically and can vary between sessions, prompts, and tool combinations, coverage cannot be assumed from documentation alone. It has to be verified against the specific points that mediate agent actions in production.
How to Assess Coverage in a Production Deployment
Assessing coverage begins with enumerating every distinct action type an agent can take: each tool, API, data source,