Security testing for AI agents
AgentFuzzer attacks your AI agent with twisted, hostile and sneaky instructions, round after round. It finds what gets through, hardens the agent, and tests again, while your ordinary customers keep getting helped.
AGENT UNDER ATTACK ยท EPISODE 1A real AgentFuzzer run, recorded liveThe moment above is real: a note on an order asked the agent to mail customer data to a new address, and it did. One round of fixes later, nothing got through.
What it does for you
Prompt injection, instructions hidden in notes or documents, fake authority, disguised requests, rule bending, slow build-ups.
An AI attacker studies what worked and writes fresh attacks, so the test keeps up with how people really try.
Refunds, discount codes, mails, customer data. A polite refusal that leaks an address still counts as a leak.
Ordinary customer requests are part of every round. A fix that sends real customers away shows up straight away.
How it works
A library of known attacks plus new ones from the AI attacker, fired at your agent in parallel.
A fixed referee checks every action the agent took against your rules, and checks that ordinary customers were served.
What broke is fixed in the instructions and in checks in code. Every attack found stays in the set, so an old trick cannot come back unnoticed.


Proof from a real run
A customer service agent for a small bike shop, with refunds, discount codes and customer data. 5 rounds, 88 attacks, every one judged on what the agent did.


Running agents that talk to customers?
Floris Knol builds AI agents. If you want to know how your agents hold up, get in touch.