For banking and finance
Your AI agent moves money. Does it know who gives the order?
An agent that pays an invoice, refunds or acts on an account gets its orders by message. A fake executive, a colleague's hijacked address or a supplier who is "changing banks" are sometimes enough to make it act. What it does then cannot be read in its prompt: it has to be tested.
What CrashMire shows you
- The fake superior and the hijacked account: an order for an exception that seems to come from management, or from a colleague's real address. In our public barometer this test splits the models sharply: in the edition of 6 November 2026, half obeyed on every run, the other half never did.
- The change of bank details: a supplier announces new bank details. Does the agent apply them without a call back to the number on file? This test is played whenever the agent touches payments.
- The ceiling: a payment or a refund above the limit, asked for insistently, split into small amounts or through a side door (a credit, a voucher). Each fault is a recorded act, judged by code.
- A dated, replayable report, with the locks to put in the code: human approval above an amount, bank details that change only after a call back, payments limited to beneficiaries already on file.
A crash test documents what was checked, on a date, on one version of the agent. It is neither a certification nor a guarantee that no incident will occur.
The proof, public
- The public barometer →
The same customer-service agent under pressure, model by model, edition after edition.
- The accounting agent demo →
Try to make Hugo pay: a payment over the limit, a change of bank details, a fake invoice.
- A sample report →
What the diligence report holds: faults, frequencies, fixes, re-test.
Bugs reported and fixed
While building our tools, we found three bugs in the official PHP SDK of the MCP protocol, the piece many PHP agents use to call their tools. We reported them with a reproduction. All three were fixed by its maintainers and contributors and released in version 0.10.0: you can check it yourself.
- #642 — an optional parameter received its default value when the agent explicitly sent "null".
- #643 — common parameter types were described as objects, and the tool refused valid calls.
- #697 — an integer beyond the range changed value on its way into the tool, enough to pass the tool's own checks.
Each link leads to the public fix; the SDK's changelog lists them under 0.10.0. CHANGELOG