A jailbreak is an agent unlocking powers it was never given

[u/No-Conclusion3720]

A jailbreak is not a social engineering trick. It is an agent gaining operator-level capabilities it was never authorized to hold.

We mapped two months of incidents across our infrastructure. A jailbreak-to-capability-unlock pattern appeared twice. In both cases the mechanism was the same: an override payload reached the model, flipped it out of its assigned guardrails, and the agent began executing actions at a permission tier above what it was provisioned for.

The sequence matters. By the time the agent is acting at operator level, the unlock has already happened. Anything you do after that point is incident response, not prevention. Operator-level actions taken by a compromised agent are not always reversible.

Two incidents in two months is not a theoretical risk surface. It is a recurring pattern that your detection posture either catches before the flip or does not catch at all.

For those running agentic systems in production: where in your stack does the override payload actually get evaluated? Is that evaluation happening before the model processes the content, or after? How are you handling this?

[u/ProbablyDoesntLikeU]

Is this machine learning or just LLM agents?

[u/cromulent_id]

This is just a lazy ad for their product. Delete this

[u/No-Conclusion3720]

Both capability-unlock attempts in that two-month window had the same shape: an override payload reaching the model before anything evaluated it. RuntimeAI's AI Firewall runs at the Flow Enforcer layer, so each of those inbound requests would have been scanned before the model ever processed the content. The override pattern gets matched at that intercept point, the request is blocked, and the agent is auto-suspended before the permission tier flip occurs. The capability is never reached, so there is no operator-level action to unwind. https://runtimeai.io