Docs
relyance.ai ↗
Browse docs

Runtime Guardrail

Updated November 17, 2026View as Markdown ↗

Overview

Runtime Guardrail applies controls to an agent in production. It uses the findings from evaluations to decide where controls are needed.

Many guardrails check only the user's input and the agent's final reply. Agents often fail between those two points: a tool returns content that contains instructions, or the agent passes sensitive data to a tool that sends it outside your organization. Runtime Guardrail also inspects tool calls and tool results.

Where Runtime Guardrail inspects an agent A request flows to the agent, the agent calls tools and data stores and receives results, and a reply flows back. Runtime Guardrail wraps the agent and inspects four moments: the request, each tool call, each tool result, and the reply. At each moment it can allow, monitor, sanitize, redact, block, or require approval. Requester User or system Runtime Guardrail Your agent No prompt changes Tools and data stores 1 2 3 4 Inspection points 1 The request 2 Each tool call 3 Each tool result 4 The reply

How enforcement works

Runtime Guardrail wraps the agent and inspects four points: the request, each tool call, each tool result, and the reply. It does not change your prompts. Each inspection is recorded as a span in your traces.

Runtime Guardrail uses the agent's attack surface to make decisions. It knows which inputs are untrusted, which data is sensitive, which tools can send data out, and what each requester is allowed to do. For example, it can allow an agent to email an order confirmation and stop the same agent from emailing a customer list because a free-text field told it to.

Mitigation options

Each finding from an evaluation has mitigation options. Select one for each finding:

Mitigation Effect Use when
Monitor only Logs each detection and allows the call You want to observe before you enforce
Sanitize instructions Removes instructions from untrusted text before the model reads it. The run completes The agent must read untrusted content
Redact sensitive data Replaces sensitive data with placeholders. The call runs The action is acceptable but the data is not
Require approval Holds the call until a person approves it A person must review high-impact actions
Block the call Stops the call The action must not happen. This option can also stop legitimate work

Test a mitigation before you enable it

Relyance replays each mitigation option in the sandbox. It uses the security tests for that finding and the related normal tasks. The result shows how many attacks still succeed and how many tasks still complete, so you can compare the options before you enable one.

Approvals

When a mitigation is set to Require approval, Runtime Guardrail holds the call and sends a request to your approvers:

  • In the app, on the agent's Guardrail tab
  • In Slack
  • Through a webhook, for your own approval or ticketing system

The same request appears in each channel. The first response decides the request. An approver can select Approve redacted, which replaces sensitive values with placeholders and then allows the call. If no one responds within the time limit that you set, the request is denied.

Use detections as tests

You can promote detections from production traces into test cases. The next experiment then includes them.