Sensitive topics
Configuration, evaluation scope, and practical limits for sensitive_topics.
sensitive_topics is the policy type used by the API and policy editor.
What it checks
Checks input and optional output for the configured sensitive-topic categories.
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:
{
"topics": [
"suicide or self-harm",
"drug abuse",
"weapons and violence",
"child exploitation",
"terrorism",
"eating disorders"
],
"threshold": 0.6,
"check_output": true
}Scope and limits
The check uses bounded text and may flag a topic without establishing its context. Sensitive-topic detection does not determine user intent, clinical risk or the correct response. Support, education and crisis resources need context-aware product decisions and representative testing.
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.