Read path
Identify every source the model can ingest before it decides on an action.
Defense guide
The hard part is not spotting bad prompts in a lab. The hard part is building a system where untrusted text can be read without automatically becoming a permitted action.
AI Agent Security
Any place the agent can read untrusted text is a possible steering surface. That includes emails, tickets, documents, web pages, internal chat, and even outputs from other tools.
Identify every source the model can ingest before it decides on an action.
Figure out which inputs can affect a later tool call.
Mark data that should never be used as a justification for action without extra checks.
Content from outside the trusted boundary should be treated as adversarial until proven otherwise.
AI Agent Security
The strongest defense is not a single prompt tweak. It is a stack of controls that make it harder for one bad instruction to become a bad action.
Keep untrusted text separate from execution policy and system instructions.
Limit which tools exist in the first place.
Decide at runtime whether the action is allowed.
Track denied and allowed actions so you can see the failure modes that keep repeating.
AI Agent Security
A defense is only real if it holds under test. That means adversarial inputs, repeated attempts, and situations where the model is confident but wrong.
Test whether the agent can be nudged into changing a tool call, changing a destination, or leaking data it should have left alone.
Repeat the test after every material change to the tool set, because a new tool often opens a path that did not exist before.
Next step
VEX Protocol helps make the action boundary explicit so the model can suggest without automatically being allowed to execute.
Sources
The main public risk framing for prompt injection.
Useful governance framing for risk reduction.
Helpful context for tool-connected agents.