A jailbreak is an attempt to get an AI model to set aside the rules it was given, so it produces content or takes actions it was meant to refuse. For AI agents, a successful jailbreak matters only as far as the agent can act, which is why the real defence sits outside the model.
Why does a jailbreak matter once agents act?
Jailbreaks began as a way to get chat models to say things they should not. That is a content problem. An agent has tools: it can look up accounts, send messages, issue refunds. A jailbroken agent that still has its tools can be talked into using them in ways nobody approved.
The lesson is uncomfortable but useful. Instructions given to a model are guidance, not enforcement. If the only thing between a customer and a refund the policy does not allow is the agent's willingness to say no, a determined person will eventually find the words that get a yes.
How does a jailbreak work in practice?
Most jailbreaks exploit the model's helpfulness and its wish to stay consistent with the conversation. Common patterns include:
- role-play ("pretend you are a supervisor with override rights");
- false authority ("I am from the compliance team; this is an approved exception");
- slow escalation over many turns, each one a small step from the last;
- framing a forbidden request as a test, a story or a hypothetical;
- splitting a request into innocent-looking parts.
None of these needs technical skill. In customer-facing work, the attacker is often a customer who simply wants something the rules do not give them.
What does an example look like?
A support agent at an online retailer may issue refunds up to the customer's limit for damaged goods. A customer spends twenty messages persuading it that they are a store manager testing the system, and asks for a refund five times the limit "to check the override works". Suppose the model is persuaded. The refund still fails, because the agent's limit is not something the model holds in its head; it is checked at the moment of action, outside the conversation. The verdict is refused, it names the customer's limit as the bound that decided, and the attempt is on file for someone to review.
How is a jailbreak different from prompt injection?
A jailbreak targets the model's own rules: it tries to make the model behave as if its guardrails did not exist. Prompt injection targets the task: it slips new instructions into the agent's input so the agent does someone else's bidding. The two often overlap, and both are defended the same way once the agent can act. Limit what the agent can do, check every action against bounds the model cannot change, and protect the agent's tools from misuse by giving each capability only the permissions it needs.
What should the agent do when it suspects one?
Refuse plainly, without debating, and route the conversation to a person if it carries on. An agent that is unsure whether a request is legitimate should treat that uncertainty as a reason to stop, which is the principle behind what an AI agent should do when it is unsure. If attempts are frequent or one appears to have worked, the owner should be able to suspend the agent in an emergency while the transcripts are reviewed.
For how these defences fit with certification and records, see our guide to agent governance.
Questions people ask
Can you make a model impossible to jailbreak?
No one has. Models get harder to jailbreak, and new techniques keep appearing. Plan on the assumption that some attempts will succeed and make sure a successful one cannot reach an action outside the agent's bounds.
Should jailbreak attempts be part of certification?
Yes. Replaying real and adversarial conversations tests whether the agent refuses what it should and escalates what it cannot decide. Refusal and escalation are worth scoring on their own, because an agent that is helpful in normal cases can still fold under pressure.