TL;DR: Zero clean defenders turned up across 14 models in ClawSecure's indirect prompt injection tests according to ClawSecure. Tool calls and delegated access need verification below the model if hostile content can steer agent actions.
Editorial analysis by NHI Mgmt Group, based on content published by ClawSecure: “Indirect Prompt Injection: 14 Models Obeyed the Attacker”.
Key questions
Q: Why does prompt injection become more dangerous as LLM agents connect to tools and data sources?
A: Prompt injection becomes more dangerous because the agent is no longer just generating text.
Q: How do security teams know if an AI agent has too much access?
A: Look for agents that can reach multiple systems without task-specific limits, use persistent tokens, or touch high-value services such as email, chat, cloud consoles, and file stores.
Q: What breaks when AI agents can call tools after reading untrusted content?
A: The system stops being a text processor and becomes an execution surface.
Practitioner guidance
- Constrain agent authority to task scope Give every agent only the minimum tool and data access needed for the current task, and expire that access immediately after use.
- Inspect untrusted content before it reaches the model Quarantine external emails, documents, tickets, and links so hostile instructions cannot enter the agent's working context unchecked.
- Separate model output from tool execution Require a policy layer to approve or deny actions before the agent can call MCP-connected tools, send data, or follow links.
Bottom line: Indirect prompt injection works because the agent trusts hostile content enough to treat it as operational context.
Glossary terms: Indirect Prompt Injection, Model Context Protocol, Agent Authorization, Delegated Authority Drift
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Indirect prompt injection is not a model-safety issue alone, it is an identity and authority problem. The decisive failure is that the agent is allowed to treat external content as instructions while holding enough privilege to act on them. Once that happens, the security boundary is no longer the model output, it is the delegated authority behind the output. Practitioners should therefore govern what the agent may believe, what it may touch, and what it may execute as one control plane.
A few things that frame the scale:
- According to PwC, 79% of organizations have already adopted AI agents to some degree.
A question worth separating out:
Q: Should organisations use prompt filtering or action-boundary controls for agent security?
A: They should use both, but for different jobs. Prompt filtering reduces opportunistic noise and cheap attacks, while action-boundary controls stop coerced behaviour inside approved workflows. If the system handles untrusted input and can write, call tools, or reach sensitive systems, the action boundary is the control that matters most.
👉 Read our full editorial: Indirect prompt injection shows governance must sit below the model