IntSen

Learn · Guardrails

AI guardrails, explained

IntSen team · Updated 12 November 2026 · 7 min read

Short answer

AI guardrails are automated checks applied to what goes into and comes out of an AI model: prompts, responses and the tool results agents read. They look for problems such as prompt injection, personal data, secrets and harmful content, and then record the finding, mask the sensitive part, or block the call.

Common questions

What is the difference between guardrails and evaluations?

Guardrails act on each call as it happens: they record, mask or block. Evaluations score quality, such as whether an agent completed the user's goal, usually on a sample of turns or on test suites before release. Most teams need both.

Should guardrails run on tool results?

Yes, for agents. Instructions injected into a web page, email or document reach the model through tool results, so checking only the user's prompt misses a common attack path.

Do guardrails slow down AI responses?

Each check takes time, and model-based checks take more than pattern matches. Run the checks you need, measure them on your own traffic, and use record mode first to see their effect before enforcing them.

Can we write our own guardrail rules?

Most guardrail systems allow custom rules, either as patterns or as plain-language instructions checked by a model. Start them in record mode, because custom rules are where false positives are most common.

Ready to make your enterprise AI accountable?

See how IntSen can help your teams govern access, safety, quality and spending across the AI applications and agents you already run.