What are the guardrails of an AI agent?

They are the limits you decide: what the agent can touch, what it must ask you about, and what it can never do.

AIR Editorial Team
How do you stop an AI agent from doing things it shouldn't?With guardrails: technical limits on which tools the agent can use, with what permissions, and which actions must go through a person. OWASP recommends giving the agent the bare minimum of extensions and permissions, and having a human approve high-impact actions 1.

The guardrails of an AI agent are the limits that set what it can do, with what permissions, and when it must stop and ask a person.

An AI agent does not just answer questions: it uses programs, reads and writes data, sends messages. The more it can do, the more damage it can do when it gets something wrong.

The risk guardrails cover

OWASP, the organisation that catalogues software vulnerabilities, calls this risk "excessive agency" and breaks it into three parts: too many functions, too many permissions, too much autonomy 1.

There is also a subtler risk, prompt injection: instructions hidden inside a text the agent reads, such as an email or a web page, that try to make it do something else 2. An agent that reads your incoming mail also reads the emails written by people who want to trick it.

The guardrails that matter for a business

These follow OWASP's recommendations 1:

  • Only the tools it needs. If the agent prepares quotes, it does not need access to everyone's mail.
  • The lowest permission possible. Being able to read the management system does not mean being able to change it.
  • A person approves high-impact actions: payments, messages sent to customers, deletions.
  • Actions are logged, so you can work out what happened.

Questions to ask the provider

Before you sign, ask in writing: which systems does the agent access, and with what permissions? Which actions does it take on its own, and which does it ask me to approve? Where can I see what it did yesterday? How do I switch it off?

If the answers are vague, there is no guardrail.

Frequently asked questions

Are guardrails set by the model's maker or by the provider?

Both. The model's maker puts general limits on the model. The ones that matter for your business (which apps, which permissions, which approvals) are configured by whoever installs the agent, and they need to be decided with you.

Can an agent with guardrails still make mistakes?

Yes. Guardrails do not make the agent infallible: they limit the damage it can do when it gets something wrong.

Read next

Want an agent with limits written down in black and white? Let's talk.

Sources

  1. OWASP, LLM06:2025 Excessive Agency, https://genai.owasp.org/llmrisk/llm062025-excessive-agency/
  2. OWASP, LLM01:2025 Prompt Injection, https://genai.owasp.org/llmrisk/llm01-prompt-injection/

Text created with the support of AI. Method and content are AIR's.

Talk to us