By Pramin Pradeep, Co-founder & CEO, BotGauge AI
For most of the last few years, my job was making software prove it works. At BotGauge, we built autonomous QA that tested our customers' apps before every release. Then those same customers started shipping AI agents, and the old playbook stopped being enough.
A test suite asks one question: does this do what it should? An agent needs a second one: what will it do when someone wants it to misbehave? That second question is red teaming. It's why we launched our agent red-teaming platform on October 28, 2026 and the developer community noticed: it finished #3 Product of the Day on Product Hunt.
Red teaming isn't new. It started as military war-gaming, became a staple of security teams paid to break in, and with LLMs turned into jailbreaking chatbots.
Agents raise the stakes because they act. They call tools, read inboxes, write to databases and hand tasks to other agents. A bad chatbot answer is embarrassing. A bad agent action is an incident.
And adoption is outrunning testing. Gartner predicts 40% of enterprise applications will feature task-specific AI agents by the end of 2026, up from under 5% in 2025. Yet most teams I talk to test agents like APIs: happy paths, a few edge cases, a vibe check. None of that simulates an adversary.
OWASP ranks prompt injection as the top risk for LLM applications, but for agents it's only the front door. Here's what we see:
• Indirect prompt injection: instructions hidden in a web page, PDF, email or support ticket the agent reads mid-task.
• Tool misuse: tricking the agent into calling a legitimate tool with harmful arguments, like a refund, a delete or an outbound email.
• Data exfiltration: coaxing the agent into leaking customer data, system prompts or credentials through its outputs or tool calls.
• Goal hijacking: slow, multi-turn manipulation that drifts the agent away from its task without tripping any single-message filter.
• Multi-agent cascades: one compromised agent passing poisoned context to others that trust it by default.
Our autonomous QA product had paying customers and a working business. But functional testing was maturing fast, and the problem our customers kept raising wasn't "does it work?" It was "can I trust it in production?"
So we rebuilt BotGauge as an Agent Control Plane, and made one calls early:
● Red teaming at the core, not a checkbox. Observability tells you what happened. Red teaming tells you what could happen, before a user or attacker finds it.
The goal is simple: attack your agent the way an adversary would, every time it changes, and show you exactly where it broke.
• 200+ custom attack strategies spanning injection, tool misuse, exfiltration, goal hijacking and jailbreaks, run against your real agent, not a sandboxed copy of the model.
• Full tracing: every failed attack links to its trace, so you see which input, which step and which tool call went wrong.
• Evals that persist: results are scored and compared across releases, so a fix doesn't quietly regress next sprint.
• Fits your stack: it sits on top of runtimes like LangGraph and AWS Bedrock AgentCore instead of replacing them.
Your agents will be attacked. Regulators are already moving: NIST's AI risk guidance and the EU AI Act both call for adversarial testing. The only real question is who finds the holes first, your team or someone else. I'd rather it be you.
Pramin Pradeep is co-founder and CEO of BotGauge AI, an Agent Control Plane for testing, observing and governing AI agents in production. BotGauge is backed by Surface Ventures, IA Seed Ventures and Saka Ventures. *
Sources
This story was distributed as a release by Jon Stojan under HackerNoon’s Business Blogging Program