TL;DR: Agentic AI red teaming, Mindgard reports, is shifting from single-prompt checks to continuous assurance across tools, memory, retrieval, and delegated actions. Runtime authority now needs tighter governance because prompt defense alone does not contain misuse once systems can act across sessions and external systems.
Editorial analysis by NHI Mgmt Group, based on content published by Mindgard: “AI Red Teaming Trends: What Security Leaders Need to Prepare for Next”.
By the numbers:
- fully automated jailbreak agents have achieved success rates as high as 97.14% in one study.
- indirect prompt injection attacks succeed only 0.5%-8.5% of the time.
- attack success rate jumps from 13% for single-turn attacks to 92% for multi-turn conversations.
Key questions
Q: Why do agentic AI systems create more security risk than standard chatbots?
A: Agentic systems can turn model output into action, which means a bad instruction can affect code flow, tool use, and downstream state.
Q: What are the signs that voice AI red teaming is failing to keep pace?
A: Common warning signs are repeated unsafe completions, different behaviour after retraining, inconsistent handling of similar prompts, and security findings that reappear when conversation patterns change.
Q: How should security teams test generative AI systems for real-world abuse?
A: They should test the full execution path, not just the model prompt.
Practitioner guidance
- Map every agent permission and tool path Document which tools, APIs, memory stores, and external content sources each AI system can reach, then classify which actions are read-only, write-capable, or business-changing.
- Move from point-in-time tests to continuous red teaming Retest after prompt changes, retrieval changes, model changes, and workflow changes so new attack paths are found before they reach production.
- Add provenance controls to all inbound AI content Screen documents, web pages, images, and other retrieved material for hidden instructions, and separate trusted operator intent from untrusted source content.
Bottom line: AI red teaming is shifting from single-prompt testing to continuous assurance across tools, memory, retrieval, and delegated actions.
Glossary terms: Agentic AI Red Teaming, Indirect Prompt Injection, AI Governance Runtime, AI Supply Chain Security
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Agentic AI red teaming is becoming an identity problem as much as a model-testing problem. Once an AI system can call tools, retain memory, or act through delegated permissions, the question changes from “can it be tricked” to “what authority can it exercise after being tricked.” That is why governance must cover identity, privilege, and runtime boundaries together. Security teams should treat agent permissions as first-class control objects, not incidental implementation detail.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: Should organisations prioritise prompt injection defence or tool permission control first?
A: Both matter, but tool permission control usually gives the faster risk reduction when agents can already call external systems. Prompt injection is the trigger, but excessive authority is what turns a successful injection into a harmful action. Reduce the permissions first, then harden the ingestion and retrieval paths that feed the agent.
👉 Read our full editorial: Agentic AI red teaming needs continuous testing beyond prompts