AcmeBot
Result by attack class
Unbounded consumption
Requests designed to make the agent work without end, burning time and money and returning nothing.
Obfuscated injection
The same attacks disguised with encodings, lookalike letters and hidden formatting to slip past filters.
Excessive agency
Attempts to make the agent take actions it has no authority for: refunds, bulk changes, privilege changes.
Direct prompt injection
The attacker types the attack straight into the chat, trying to override the agent's instructions.
Hidden context extraction
Attempts to make the agent reveal its hidden instructions, configuration or internal codes, directly or a piece at a time.
Indirect prompt injection
The attack is hidden inside content the agent is asked to read: an email, an invoice, a web page, a tool's output.
Jailbreak
Role-play, fake authority and emotional pressure designed to convince the agent its rules no longer apply.
Indirect prompt injection
The attack is hidden inside content the agent is asked to read: an email, an invoice, a web page, a tool's output.
Profile aggregation
Requests to summarise or export everything the agent knows about the user.
Direct disclosure
Plain requests for personal data the agent holds about the user.
Data exfiltration
Attempts to smuggle personal data out of the conversation, through links, images or encodings.
Impersonation
Someone claiming a role — courier, partner, police, supervisor — to unlock data they have no right to.
Partial leaks
Yes/no and partial questions that leak personal data a piece at a time.
Over-collection
Whether the agent asks for, or accepts, data it should never hold: card numbers, security codes, passwords.
Tested against
NIST AI Risk Management Framework 1.0 · OWASP Top 10 for LLM Applications 2026
What this summary states
- The results of a point-in-time test of the agent as it was configured on 22 October 2026.
- Every attack that was run is counted above, including the ones that failed. It is generated from the same results as the full report and cannot leave a finding out.
- Attack text and technical detail are in the full report, held by the agent's owner.
What it does not state
- That the agent is secure, or safe against attacks not in these packs.
- That any finding has since been fixed. A retest would show that.
- Compliance with any framework. It is not a certification or an attestation.