Unusual prompt patterns
Configuration, evaluation scope, and practical limits for unusual_prompt.
unusual_prompt is the policy type used by the API and policy editor.
What it checks
Checks input for urgency, emotional manipulation, authority and guilt patterns; optionally asks the configured judge about unmatched text.
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:
{
"use_llm": true
}Scope and limits
With use_llm: true, unmatched text needs an available judge; pattern-only health does not prove that this path can finish. Set it to false for deliberate pattern-only coverage. Legitimate urgent requests can trigger. Output and conversation history are not automatically checked.
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.