Unsafe web content
Configuration, evaluation scope, and practical limits for web_sanitization.
web_sanitization is the policy type used by the API and policy editor.
What it checks
Detects suspicious HTML, script and related web-content patterns in LLM input and optional output.
Configure the policy
Create a policy under Dashboard → Security → Policies. Choose this policy type, set the agent scope, and start in warning mode while you measure results. Use blocking only after verifying the application’s decision gate.
The following is the config object, not a complete policy-creation request:
{
"check_output": true
}Scope and limits
Evaluation returns findings; it does not return a sanitized HTML document. Render untrusted text safely and use an appropriate HTML sanitizer at the actual rendering boundary. Do not insert evaluated text into innerHTML on the assumption that a clean result made it safe.
Verify before rollout
Test a representative safe input, a synthetic positive case, and an unavailable-detector case. Inspect evaluation_status, errors, policies_evaluated, findings and allowed. A clean empty finding list is useful only when the required checks completed.
The policy mode determines the decision: warning findings can coexist with allowed: true. Your application must act on a blocking decision before the protected operation. Evaluation does not automatically redact text or cancel an operation that already happened.