Skip to main content
Guardrails keep an agent on its job. They apply on top of your prompt, in the same way, everywhere the agent talks: phone calls, the test panel and test suites, SMS and web chat. Three rails, each on its own: When the person keeps pushing decides what happens after the agent has declined twice: keep declining and steer back (the default), or say goodbye and end the call on the third decline. On SMS and web chat the agent closes the conversation instead. Every decline is recorded: it appears in the call’s transcript and in test results as a guardrail_declined event with its reason (off_topic, manipulation or blocked_topic), so you can see how often callers run into a rail and which one.

Setting guardrails

Dashboard: open the agent, go to Behavior, and fill in the Guardrails card. API: set guardrails on the agent (null turns every rail off):
Guardrails are part of the agent’s configuration: they are saved in its versions, published with it, and copied when the agent is cloned.

Proving them

Guardrails are instructions the agent follows, so test them the way you test anything else the agent should do: in the test panel’s Chat, or with a test suite whose scripts try to pull the agent off course (an unrelated question, “ignore your instructions”, a blocked subject, insisting three times) and whose rubrics check that it declined and came back. Run each test a few times.
Guardrails steer the agent’s own replies. They do not filter what the person says, and they are not a substitute for keeping secrets out of the prompt: anything in the prompt can, in principle, be talked about, so put credentials, internal notes and prices you do not want quoted in a tool or a knowledge base with access rules instead.