🧠

Simple Guardrails

Decide what your workflow must never do — then enforce it in three layers.

AI Builder · Advanced · 15 min read · 4 quiz questions

By Ronan Liedmeier, fractional head of growth and course author · Reviewed 13 October 2026

What you will learn

  • The three layers
  • Allow-lists and deny-lists
  • "When to refuse" prompt patterns
  • Output validation
  • The human gate

Lesson preview

Prompt-level rules alone are persuasion, not enforcement — a strange input can talk its way past them. Real safety comes from three layers working together: input allow/deny-lists, prompt-level refusal patterns, and mechanical output validation, with human approval gates on anything consequential like sends, spends, or deletes. Reliable guardrails work in three layers, each catching what the others might miss. Input rules constrain what's allowed into the workflow in the first place. Prompt-level refusals teach the AI its own red lines — situations where it should stop and flag rather than proceed. Output validation mechanically checks what came out, regardless of what the prompt asked for. No single layer is sufficient on its own. Input rules can't catch a bad output from an otherwise-valid input; prompt refusals can be talked past by an unusual phrasing; output validation alone lets bad data flow in and get processed before being caught. Together, the three layers catch each other's blind spots. The simplest and most reliable guardrail restricts what can enter the workflow at all. An allow-list — only emails from a specific label, only requests from a known set of senders, only file types you expect — is stronger than trying to filter out every bad case after the fact with a deny-list. Deny-lists are useful as a secondary layer (blocking a specific known-bad pattern you've already seen cause problems), but they're inherently reactive — you can only deny what you've already thought of or already seen go wrong. Wherever possible, prefer defining what's allowed over trying to enumerate everything that's forbidden.

Continue reading

Key terms in this module

AI guardrails
AI guardrails are checks and limits placed around an AI system that block or flag unsafe or wrong inputs and outputs before they cause harm. The strongest ones run as code outside the model, so a cleverly worded request can't talk its way past them.
Human in the loop
Human in the loop is a setup where an AI system pauses at set points so a person can approve or correct its work before it takes effect. It is used for actions that are hard to undo, such as sending emails to customers or moving money.

Frequently asked questions

Who is "Simple Guardrails" for?
This Advanced module in AI Builder is for learners who already use AI daily and are ready to build their first real workflows and integrations. It takes about 15 minutes and ends with a 4-question quiz.
Do I need to code?
No traditional programming is required. You will use no-code and low-code tools, and occasionally paste a short snippet that the lesson explains line by line.
What comes before and after this module?
Before "Simple Guardrails", take "Basic Evals for Your Own Workflows" (module 6 of AI Builder). Afterwards, continue with "Connecting One MCP Server (Consumer)".

Unlock this lesson and the full academy

  • Monthly€9.99 / month
  • Yearly€69.99 / year
  • Lifetime€129.99 one time
See plansStart with the free lessons

Loading your lesson…

Related modules