What does an AI agent audit check?
Prompt injection
Whether untrusted content — user input, web pages, documents, tool output — can redirect the agent's behaviour.
Tool permissions
What each tool can reach, whether the scope is least-privilege, and which calls should require confirmation.
Authorization
Whether the agent acts with the end user's permissions or with a shared privileged identity.
Context handling
What enters the context window, whose data it belongs to, and how leakage between users is prevented.
Memory and retrieval
Persistence, tenant scoping in the vector store, and poisoning of stored context.
Output validation
Model output parsed, rendered, or executed downstream without being checked or escaped.
Loop control
Step limits, recursion guards, and stopping conditions for an agent that will not converge.
Cost controls
Per-user and global spend limits, token budgets, and the runaway loop that bills all night.
Rate and quota
Provider limits, backoff, and behaviour when the model returns 429 mid-task.
Failure behaviour
What the agent does on a tool error or timeout, and whether it fails closed or invents a result.
Determinism
Idempotency of side-effecting tools, and duplicate actions on retry.
Evaluation
Whether there is any regression suite, and whether a prompt change can be shipped safely.
Observability
Trace capture for runs, tool calls, and token spend, sufficient to reconstruct an incident.
Data retention
What is sent to the provider, what is logged, retention terms, and PII in prompts.
Human oversight
Where a person approves an irreversible action, and whether that gate can be bypassed.
Other audits
Each audit answers a different question. Most engagements combine two or three.
Build with
confidence.
AI builds the product. Vibecop makes sure it won’t break in production, fail under scale, or expose your users to risk. One audit. Fewer expensive surprises.
