# Guardrails

Guardrails are safety and compliance policies applied to agent inputs and outputs. They intercept content before it reaches the agent or before the agent’s response is returned to the user, and either block, mask, or flag content that violates the policy.

Because guardrails are Foundry resources, they are created once at the workspace level and can be applied to any number of agents. A single guardrail built by your compliance team can protect every customer-facing agent in the workspace.

OneByZero Neo supports these guardrail types, accessible from tabs on the Guardrails page:

- **In-House** — prompt-based guardrails powered by Neo’s own evaluation engine. You define a validation prompt and configure what constitutes a pass or fail result.
- **Bedrock** — integration with AWS Bedrock Guardrails, which provides managed content filtering, denied topics, word blocklists, PII protection, and contextual grounding checks.
- **NeMo** — NVIDIA NeMo Guardrails, combining pattern, policy, content safety, and topic checks. Shown only when NeMo guardrails are enabled for your deployment.

Switch between types using the tabs at the top of the Guardrails page.

**Managing guardrails**

In-House and Bedrock guardrails support:

- **Search** — find guardrails by name using the search bar.
- **Tagging** — apply tags to organise guardrails by department, use case, compliance framework, or environment (e.g. `production`, `banking`, `pii-protection`).
- **Versioning** — each guardrail displays its current version. New versions can be created while previous versions remain accessible.
- **Export / Import** — guardrail configurations can be exported and imported, enabling sharing across workspaces or promotion across environments.
- **Enable / Disable** toggle — controls whether the guardrail is active and can be applied to agents.

**In this section:**

- [In-House Guardrails](in_house.html)
- [Bedrock Guardrails](bedrock.html)
- [NeMo Guardrails](nemo.html)