I think the model itself will be jailbroken. So prevention lives in the
server, not the prompt. A control can be misscoped or misbuilt. So each risk also answers the
question defenders really have: how do I know?
Each card is a prism. Click the right half to turn it forward, the left half back. Enter or ← → also work: attack → detection → control.
ASI01 : 2026
Agent Goal Hijack
AttackInjected text in a tool result or document rewrites the agent's objective.
ASI01 : 2026
Agent Goal Hijack
Detection · SOCFlag tool-call chains where the target diverges from the session's stated task. Scan tool output for injection patterns before it influences a call.
ASI01 : 2026
Agent Goal Hijack
Control · preventTool output is structured and isolated from the system prompt. The server screens it for injection patterns and does not read it as instructions. Content cannot rewrite the goal.
ASI02 : 2026
Tool Misuse & Exploitation
AttackAn attacker bends legitimate tools into destructive or over-scoped actions.
ASI02 : 2026
Tool Misuse & Exploitation
Detection · SOCAlert on exfil-shaped sequences: a read-heavy query, then an external send. Also alert when a user crosses N× their tool-call baseline.
ASI02 : 2026
Tool Misuse & Exploitation
Control · preventA runtime endpoint allowlist (least privilege), argument validation, and rate limits for each tool. Your code rejects non-approved calls.
ASI03 : 2026
Identity & Privilege Abuse
AttackOver-broad or leaked credentials let the agent do more than its scope allows.
ASI03 : 2026
Identity & Privilege Abuse
Detection · SOCAlert when a token is used for endpoints or scopes it was not granted. Also alert when one identity suddenly reaches resources it did not touch before.
ASI03 : 2026
Identity & Privilege Abuse
Control · preventOAuth 2.1 and PKCE. Verify the JWT on each call (iss, aud, exp, sub). Use least-privilege scopes and a different token for each downstream. No ambient authority.
ASI04 : 2026
Agentic Supply Chain
AttackA poisoned tool, registry, or dependency subverts the agent.
ASI04 : 2026
Agentic Supply Chain
Detection · SOCAlert when a tool descriptor's hash changes after approval, when an unrecognized MCP server registers, or when a dependency lockfile changes.
ASI04 : 2026
Agentic Supply Chain
Control · preventPin and signature-verify dependencies. Vet MCP servers and sign tool descriptors. Keep a component inventory (SBOM). Allow no silent tool installation.
ASI05 : 2026
Unexpected Code Execution
AttackUntrusted input reaches eval or exec: remote code execution.
ASI05 : 2026
Unexpected Code Execution
Detection · SOCAlert when eval or exec paths fire, on unexpected child-process spawns from the MCP process, or when code-shaped input reaches an executor.
ASI05 : 2026
Unexpected Code Execution
Control · preventRun no eval or exec on model-influenced input. Use strict input schemas. Sandbox execution and scope it to capabilities. Deny arbitrary-code tools.
ASI06 : 2026
Memory & Context Poisoning
AttackAdversarial data written into memory poisons future decisions.
ASI06 : 2026
Memory & Context Poisoning
Detection · SOCFlag memory and RAG writes from low-trust sources. Also flag retrieval of freshly-written context that then steers a sensitive action (provenance gaps).
ASI06 : 2026
Memory & Context Poisoning
Control · preventTreat memory writes as untrusted input. Validate them and record provenance on entry. Scope them to each tenant and session. Sanitize them before you use them again.
ASI07 : 2026
Insecure Inter-Agent Comms
AttackAn attacker spoofs, tampers, replays, or injects agent-to-agent and MCP messages.
ASI07 : 2026
Insecure Inter-Agent Comms
Detection · SOCAlert on failed-auth or unauthenticated peer messages, on messages with a schema or claims validation failure, and on sudden inter-agent volume spikes.
ASI07 : 2026
Insecure Inter-Agent Comms
Control · preventUse authenticated, structured channels (mTLS or scoped tokens). Schema-validate and replay-protect each message (nonces, timestamps). Treat peer output as data, not commands.
ASI08 : 2026
Cascading Agent Failures
AttackOne compromised or failing agent cascades across the system.
ASI08 : 2026
Cascading Agent Failures
Detection · SOCWatch for error rates that move across agents, retry storms, and circuit-breaker trips grouped in a short window.
ASI08 : 2026
Cascading Agent Failures
Control · preventBlast-radius limits, circuit breakers, least privilege and rate limits for each agent, and a kill-switch backed by full audit.
ASI09 : 2026
Human-Agent Trust Exploitation
AttackAn attacker uses the agent to influence the human in the loop.
ASI09 : 2026
Human-Agent Trust Exploitation
Detection · SOCFlag high-impact actions approved with abnormally low latency (rubber-stamping). Also flag outputs with no provenance that come before an approval.
ASI09 : 2026
Human-Agent Trust Exploitation
Control · preventProvenance and citations on each output, human-approval gates on high-impact actions, and no unattended privileged operations.
ASI10 : 2026
Rogue Agents
AttackAn agent that ignores policy and runs undetected.
ASI10 : 2026
Rogue Agents
Detection · SOCAlert on an action with no matching originating-prompt hash, on work during unapproved windows, or on deviation from the agent's behavioral baseline.
ASI10 : 2026
Rogue Agents
Control · preventAudit each action and connect it to the prompt that caused it. Add anomaly monitoring and alerts, least privilege, and a kill-switch.