I've been building an open-source runtime check for AI agents' tool calls, and I wanted to see it against a real prompt injection instead of a unit test.
Setup: an LLM agent drives a procedural-generation system in Unity. I ask it to add 1,000 trees (it does). Then I hand it a design brief as a PDF. Hidden inside the PDF is an instruction to delete the entire scene, and the agent goes for it.
The call gets blocked before it runs, because the session's intent was "add trees", not "delete things". The decision is deterministic (rules, not another LLM), so you can't talk it out of it with a clever prompt.
What I'd like to know from people actually running agents:
- Do you gate destructive tool calls today? How?
- Would you rather it ask you for approval, or just block?
- What would make you trust something like this?
Honest limits: it's early. Detection is rule-based, so a determined attacker can find bypasses. My benchmark (53 attack scenarios) is hand-written by me, so treat 51/53 as a regression test, not proof.
Repo (Apache-2.0): https://github.com/aegotrax-dev/aegotrax
Site with a small in-browser demo: https://aegotrax.com
Happy to hear where it breaks :)