Skip to main content
Version: 11.5.0

Guardrails

An agent that can read can be told what to do by whatever it reads. A web page it fetches, a ticket it summarizes or a shared document can carry instructions aimed at the agent, not at you. An agent can also act: send mail, post to a channel, write to a system or run a command. Then content it merely read can become an action you never asked for. This is indirect prompt injection, and input guardrails exist to contain it.

HYPR AgentPass™ input guardrails do not try to out-argue a hostile instruction. They watch what a session has done: what it read, how sensitive that was, and where it now tries to send it. When that combination is dangerous, they hold or stop the call, however the content was worded.

In the console, Guardrails and each of its pages carry a Preview tag.

Guardrails build on the gateway you already have

Input guardrails are enforced at the gateway, alongside your policies and tool access. They apply to every kind of connector a session touches, whether an MCP server, a REST API or an AI provider, so a session cannot sidestep them by switching tools.

The Pieces​

Input guardrails are a set of controls that work together. Each has its own page.

ControlWhat it doesRead more
The Rule-of-Two breakerHolds or stops a call when a session that read untrusted and sensitive data reaches a way out. A held call raises an approval that carries its evidenceThe Rule-of-Two Breaker
Tool-definition integrityFlags a tool whose definition changes after it was approved, and raises an alert. With quarantine turned on, agents also lose the tool until a person approves the changeTool-Definition Integrity
Alerts and containmentTurns a guardrail enforcement into a deduplicated, budgeted alert, gives security operations a triage queue, and lets a responder contain the agent behind an alertAlerts and Containment
Posture and historyShows what the guardrails have done and what still waits on a person, and trends that activity over timePosture and History
The session investigatorReads Session watch findings and, once you let it, pauses or terminates a coding-agent sessionThe Session Investigator
Bring-your-own judgesAn optional layer that asks a model you choose about the content behind a held or stopped callBring-Your-Own Judges
The Proving GroundRuns a scripted attack pack against an isolated sandbox, and shows which attacks the guardrails held or stopped, off versus onThe Proving Ground
SettingsAlert volume, containment, tool quarantine, approval timeouts and the session investigatorGuardrail Settings

In the console, these pages sit under Guardrails in the sidebar: Posture, Alerts, History, Proving ground, Session investigator, Judges and Settings. You see the entries your permissions allow. See Who Manages Guardrails.

How the Breaker Reasons​

Three facts about a session decide whether the breaker acts. You do not compute them. The gateway tracks them as the session runs.

  • Trust. Every connector has a Source trust setting. It is Untrusted by default. Mark a connector Trusted, with a recorded reason, only when its content comes from a source you control. One read from an untrusted source marks the session untrusted for the rest of its life.
  • Sensitivity. Tool reads carry a sensitivity tier from your data classification. A session's sensitivity only rises. Reading Confidential data once keeps the session at that level.
  • A way out. Each tool has a sink: external communications, a state change, a credential or code execution. A read is not a sink; sending an email is.

When a session has read untrusted and sensitive data, and then reaches an external-communications or state-change sink, the breaker acts. The Rule-of-Two Breaker explains what happens next.

Turning Guardrails On​

You adopt input guardrails deliberately, so you can see what they would do before they do it. Both steps need Data labels: Manage, which Admin holds out of the box.

  1. Turn on session tracking. The breaker needs to know what each session has read. Turn it on from Settings → Data classification. With it off, the session.* facts the breaker relies on are absent, and the guardrail rules never match. See Session Tracking.
  2. Adopt the guardrail starter policies. Open Settings → Data classification, and click the Policies tab. It lists four guardrail- starters beside the classification and session starters. Preview matches shows how many calls a starter would have matched in the last seven days. Add this policy creates it in observe mode, so it records what it would have held or stopped without changing traffic. Switch it to enforce once you trust it. See How Policies Are Evaluated.

The Policies tab of Settings → Data classification now shows each guardrail- starter as Already added.

Alert, containment, approval, tool-integrity and session investigator behavior is set on Guardrails → Settings. See Guardrail Settings.

Who Manages Guardrails​

What you see under Guardrails follows your permissions.

PermissionLets youOut of the box
Guardrails: ViewOpen Posture, Alerts, History, Proving ground and Session investigator, and export evidenceAdmin, Operator, Security analyst, Auditor and Model governance owner
Guardrails: ManageWork alerts, contain agents, run the attack pack, mark a session pause a false positive, and open SettingsAdmin and Security analyst
Settings: Edit, with Guardrails: ManageSave guardrail settings and per-agent overridesAdmin
Model governance: ViewOpen JudgesAdmin, Security analyst, Auditor and Model governance owner
Model governance: ManageRegister, promote and bind judgesAdmin and Model governance owner

Security analyst triages and contains, and reads broadly, but cannot change policies, settings, connectors or credentials. Auditor reads and exports, and changes nothing. Model governance owner governs judges. See Roles for Security Operations, The Model Governance Owner and Permissions by Role.