If your agent reads email, web pages, tickets or documents and can then call tools, someone outside your company can put instructions in front of it. We test whether those instructions can make it leak data or take actions your users never asked for, and we tell you exactly what to change.
Email us about a reviewCodes refer to the OWASP Top 10 for LLM Applications.
A written report. Each finding has a severity, steps to reproduce it, the impact, and a specific fix, ordered by risk.
send_email with the account history attached, without asking anyone.Illustrative example of the report format, not taken from a client engagement.
One agent or MCP server, three business days. Includes a short findings call or Q&A by email. This is a first-client rate, normally $1,500, in exchange for a short testimonial if you're happy with the work.
About a week across several agents, tools or workflows. Adds automated attack suites, a review of your guardrail and permission design, and a retest after you ship fixes.
The tooling behind the review is our own and the results are public.
| Result | Ours | Comparison |
|---|---|---|
| Indirect-injection detector, AgentDojo AUC | 0.984 | 0.793ProtectAI v2 |
| Same benchmark, false-positive rate | 0.031 | 0.333ProtectAI v2 |
| Agent benign tasks completed with the detector deciding what to quarantine | 70 / 97 | 32 / 97without the detector |
| Injection attacks that succeeded in that setup | 0 / 200 | 0 / 200without the detector |
Sources: the detector on Hugging Face, the agent benchmark write-up, and the harness comparison.
Reviews are done by Ashton Damrel, who ran an AI agent with production access as a company's sole engineer and designed its guardrails. Portfolio.
Email sales@ascensiontechsolutions.com with what your agent does and which tools it can call. We reply within one business day with a proposed scope and start date.