Walk a breach chain end to end.
Each chain shows the local checks that pass at each step and the composed outcome that exceeds approved scope.
Chain library.
Prompt injection to tool misuse
Hidden directives in user input become attacker-chosen tool parameters before any policy check fires.
Read → INFLUENCEPoisoned retrieved context
A planted document is ranked highly and treated as authoritative evidence for a high-impact decision.
Read → INFLUENCEHidden instruction in document ingestion
Concealed directives inside ingested documents override policy and invoke tools the user never asked for.
Read → ACTIONCode-execution side effects
Visible output looks fine while filesystem writes, network calls, and leaked secrets quietly accumulate.
Read → AUTHORITYCredential overreach
An over-broad token is reused to invoke an unrelated tool, expanding impact beyond the user's intent.
Read → STATEMemory poisoning
A poisoned fact written in one session is later retrieved as trusted state and shapes a future decision.
Read → CAPABILITYUnsafe MCP / tool extension
A capability added without registry review or scope check opens a path to high-impact downstream actions.
Read → PROPAGATIONAgent-to-agent contamination
One agent's manipulated output flows through orchestration into another agent that treats it as trusted input.
Read → GOVERNANCEFake approval loop
A polished summary hides the real tool parameters and diff, so the human approves a sentence, not the action.
Read → GOVERNANCEWorkflow automation abuse
Many in-policy steps compose into broad effective authority and an irreversible action no single step would allow.
Read → TEMPLATEAttack chain template
The standard template every chain in this library is built from.
Read →