AI Agent Incident Tracker

By authorization boundary

Where an independent check would sit

The boundary each write-up identifies. Select a row to filter the list.

1. Tool-Call Gate125
2. Runtime Gate46
3. Credential Gate42
4. Deploy Gate18
5. Data Mutation Gate8

Reported events Controlled demonstrations

Whose agent was acting

Would an independent gate have held it?

Our assessment, made per record. It is analysis, not a measurement.

1. The operator's own agent158 of 239

   An agent acting inside the affected workflow.

2. An attacker's agent60 of 239

   Run by the threat actor, outside any internal boundary.

3. No agent took an action21 of 239

   Supply-chain, platform, and credential events with no agent action to hold.

Yes 43Partial 115No 78Unknown 3

Yes and Partial describe records where the operator's own agent acted. 76 of the 78 No assessments involve an attacker's agent or no agent action at all, which an internal gate cannot hold.