#058Technical3 min
Audit an AI agent’s security
Scope an authorized agent review around instructions, tool permissions and evidence of leakage.
Hackaiz team · updated 21/11/2026

01Identify what the agent can actually do
An agent is more than a chat window when it can call tools, fetch addresses or act on application data. Begin the security review with its capabilities: which tools can read, write, delete or send information, and which credentials those tools use. A polite refusal in one conversation is not evidence that these permissions are enforced by the application. Review the code and the authorized endpoint as separate sources of evidence.
Hackaiz’s AI-agent guide covers instruction injection, excessive tool permissions, internal-network access through URL-fetching tools, key leakage and authentication weaknesses. Instruction injection means content tries to redirect the model away from the task or its governing instructions. Internal-network request abuse, often called SSRF, means a fetching tool reaches addresses that should not be available to the user. These are specific review areas, not a promise to test every possible conversation.
03Read prompts, responses and code locations
For an AI finding, the evidence is the prompt sent and response received, or the exact code location. For example, a URL-fetching helper without an appropriate destination boundary raises a different question from a response that reveals private context. Keep the observed behavior separate from what you suspect could happen. A secret written into a log, echoed in a reply or sent to a user-controlled address also requires understanding the specific data path.
If an endpoint is unreachable, the report says the check did not run rather than declaring the agent safe. The application report uses Danger, To fix and To watch to organize findings. Check coverage alongside these groups: no finding on an untested tool does not validate that tool’s permissions. Review default authentication and fallback keys in code as well, because a robust model instruction cannot compensate for an unauthenticated application boundary.
Frequently asked questions
Take the next step
Was this article helpful?