Guardrails — AI Glossary

Reference details

Related terms

• Hallucination
• Jailbreak
• Prompt Injection
• AI Alignment

Example: Two checks, two directions

Inbound, a guardrail scans the user message for an injection attempt and refuses before the model ever sees it. Outbound, it validates the response against a schema and scans for anything resembling a card number or national ID; a failing response is regenerated or blocked rather than returned. Both sit outside the model, which is what makes them enforceable.

Commonly confused with

Guardrails are not alignment. Alignment shapes what the model tends to do during training; guardrails are runtime checks that hold whether or not the model cooperates. A well-aligned model still needs guardrails, because alignment is a tendency and a guardrail is a control.

When to use it

Reach for it when:

• Output flows somewhere consequential — a customer, a database, a payment
• You must be able to show an auditor what was enforced
• The input is user-controlled and may be adversarial

Reach for something else when:

• As your only defence: guardrails are filters, and filters are bypassable
• On internal prototypes, where they mostly slow iteration
• As a substitute for permissions — a check that says no is weaker than an action that cannot be taken

Referenced by

This term is used by the following ModelRefs references:

• guardrailed agent
• human in the loop
• sandboxed code execution
• file read tool
• file write tool
• tool approval gateway
• tool rate limiter
• multi agent orchestration stack
• hybrid private cloud stack
• byo model gateway stack

Continue your research

Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Guardrails — AI Glossary.

• Browse models
• Review providers
• Inspect benchmarks
• Explore workflows
• Learn AI concepts
• Read decision guides
• Review trust and methodology
• Start a decision path