Evaluates content or an agent action against the tenant’s configured safety guardrails. The guardrails engine checks the input against all applicable policy rules and returns a deterministic allow/deny decision with detailed violation information. Guardrail checks are designed for inline use within orchestration flows. They execute in under 50ms for most rule sets, enabling real-time safety enforcement without significant latency overhead.Documentation Index
Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
Use this file to discover all available pages before exploring further.
Circuit Breaker
The guardrails system includes a circuit breaker that automatically escalates to deny-all mode when the violation rate exceeds a configurable threshold within a rolling window. Thecircuit_breaker_status field in the response indicates the current state.
Authentication
API key with
guardrails:check scope. Alternatively, pass a Bearer JWT token
in the Authorization header.Tenant identifier for multi-tenant isolation.
Request
MAIP agent identifier requesting the guardrail check.
Text content to evaluate against content safety rules. Provide either
content or action_type (or both).Action the agent intends to perform (e.g.
send_email, modify_record,
external_api_call, financial_transaction). Evaluated against action-level
policy rules.Additional context for rule evaluation. May include: -
orchestration_id
(string) — Parent orchestration for audit linkage - step_name (string) —
Current workflow step - target_resource (string) — Resource being acted
upon - user_id (string) — End user associated with the action - Any custom
key-value pairs referenced by policy rulesResponse
Whether the content/action is permitted.
true if no violations were found,
false if any blocking violation was triggered.Array of rule violations found. Each violation contains: -
rule_id (string)
— Identifier of the triggered rule - severity (string) — Violation
severity: info, warning, error, critical - message (string) —
Human-readable description of the violationCurrent circuit breaker state:
closed (normal operation), open (deny-all
mode active), or half_open (recovery testing).Total number of rules evaluated during the check.
Time taken to evaluate all rules in milliseconds.

