Documentation Index
Fetch the complete documentation index at: https://docs.sirenspec.dev/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Guardrails run on every node execution — checking input before it reaches the LLM and validating (or transforming) output before it is written to the context. By default, theinjection guardrail is active on all agents. You can configure guardrails at the workflow level, per agent, or disable them entirely.
Built-in Guardrails
injection
Detects common prompt-injection patterns in both input and output text.
If an injection signature is detected, the node fails immediately with a GuardrailViolation and the workflow status is set to "failed".
Detected patterns include:
ignore previous instructionsdisregard your instructionsyou are now [role]forget your instructionsnew instructions:override previous instructionsact as a [role]pretend you are [role]your new role issystem: you are
injection.
length
Limits the length of LLM output. In the default "truncate" mode, responses longer than the limit are silently cut and appended with "...".
| Parameter | Default | Description |
|---|---|---|
max_chars | 4000 | Maximum allowed output length in characters. |
mode | truncate | "truncate" appends "..." and trims; "raise" raises a GuardrailViolation. |
The
length guardrail only checks output — input is passed through unchanged.Configuration
Workflow-level (default for all agents)
guardrails is omitted from the workflow file, only injection is active.
Per-agent override
An agent’sguardrails field completely replaces the workflow-level list for that agent:
Disabling all guardrails
Set an empty list to disable all guardrails for the workflow or a specific agent:Execution Trace
Guardrails that pass are recorded in each node’s trace entry:GuardrailViolation sets the node’s error field and the workflow summary.status to "failed":