cookbook proof · vulnerability-escalation-guard
Vulnerability escalation
A customer-ops team keeps acting after a vulnerability signal.
Agno Teams FCA Consumer Duty TAKE_ACTION
without kiff 6 actions A whole team keeps acting on a flagged customer.
TAKE_ACTION state-aware gate ↓
with kiff 1 action Team halted the moment the flag lands.
1 Agent proposes
TAKE_ACTION on a Case.2 KIFF reads the Case's current state — before anything runs.
3 First call: state allows it → executed, receipt signed.
4 State is now
VULNERABLE_FLAGGED → every repeat refused, receipt signed.The scenario
A customer-ops team — several agents on one case — keeps taking routine actions after a vulnerability signal is raised. No single agent sees the whole picture.
Why it was refused
The vulnerability flag moves the case into VULNERABLE_FLAGGED. Routine actions are not allowed in that state, so the gate halts the entire team at once — the kind of cross-agent stop FCA Consumer Duty expects.