What are interventions?
Interventions are records of when Agent Sentinel’s policy engine actively prevented or modified agent actions. They demonstrate the platform’s core value proposition: showing what disasters were avoided, costs saved, and risks mitigated.
Intervention types
Intervention outcomes
Automatic intervention tracking
Interventions are automatically tracked when:
- A policy denies an action
- A budget limit is exceeded
- Rate limiting triggers
- Human approval is required
Each intervention records:
- Action details: name, description, inputs
- Risk assessment: risk level, blast radius (impact if allowed)
- Cost metrics: estimated cost, actual cost (if executed), cost prevented
- Policy context: which policy triggered the intervention
- Agent context: agent_id, run_id
- Outcome: what happened (blocked, approved, modified, etc.)
- Rationale: why Sentinel intervened
- Agent intent: what the agent was trying to do
Viewing interventions
Interventions are stored locally in .agent-sentinel/interventions.jsonl and synced to the platform if remote sync is enabled.
View in the web console:
- Navigate to Interventions page
- See cost saved, high-risk blocks prevented
- Filter by type, outcome, risk level
- View detailed blast radius analysis
Interventions sync to the platform via the background sync service and can be queried via:
Example: Blast radius tracking
Cost prevention metrics
The platform calculates:
- Total cost prevented: Sum of estimated costs for blocked actions
- High-risk blocks: Count of critical/high-risk interventions
- Top blocked actions: Most frequently blocked action types
- Triggering policies: Which policies provide the most value
Interventions are your “receipts” - they show stakeholders exactly what disasters Agent Sentinel prevented.
See also
- Policies - Configure policies that trigger interventions
- Approvals - Human-in-the-loop workflow for escalated actions
- Compliance - EU AI Act compliance features