Skip to content

For the CIO and IT

Test what your agents do, not what they say.

Your agents are plugged into APIs, databases, mailboxes. An order hidden in a document, a fake colleague or fake support can make them cross a line. The model provider tests its model, not your agent with your tools and your permissions.

What CrashMire shows you

  • Every tool call the agent makes, recorded and judged, on inert copies of its tools: nothing runs on your side, no key or network access asked.
  • Your agent rebuilt, or your real agent plugged in over the MCP protocol, on several models or on your own endpoint.
  • A re-test at each change of model, instructions or tools, and a check that can run before each release.

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

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