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 Gate53
2. Credential Gate39
3. Runtime Gate39
4. Deploy Gate18
5. Data Mutation Gate7

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 agent114 of 156

   An agent acting inside the affected workflow.

2. An attacker's agent22 of 156

   Run by the threat actor, outside any internal boundary.

3. No agent took an action20 of 156

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

Yes 35Partial 76No 42Unknown 3

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