What Guardrails means in practice
Guardrails are the policy enforcement layer that sits around an LLM in production. Input guardrails inspect prompts for prompt-injection attempts, PII that shouldn't be sent to the model, off-topic queries, or jailbreak patterns. Output guardrails inspect responses for hallucinated facts, leaked credentials, policy violations, or PII that shouldn't reach the user. Common open-source implementations include NeMo Guardrails and LlamaGuard. In a sovereign deployment guardrails run inside the perimeter (no cloud filter API), with policy rules versioned in source control and a clean audit trail of every block. The engineering rule of thumb: every public-facing LLM endpoint has guardrails, no exceptions.
Related terms
Prompt injection →
An attack where a malicious user embeds instructions in the input that override the LLM's intended system prompt or trick it into bypassing guardrails.
Agentic AI →
Systems where an LLM acts as a planner that chooses tools, decomposes tasks, and iterates toward a goal rather than producing a single completion.
Evaluation (evals) →
Systematic testing of an AI system against a curated set of inputs to measure quality on the dimensions the business cares about — accuracy, faithfulness, safety, format.
More in this category
All 62 terms, in plain language
Sovereign AI, RAG, agentic AI, IDP, MLOps and the regulations that shape enterprise AI.