Competitor mentions
Configuration, evaluation scope, and practical limits for competitor_check.
competitor_check is the policy type used by the API and policy editor.
What it checks
Checks input and optional output for the competitor names selected in the policy.
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:
{
"competitors": [
"Example Rival"
],
"check_output": true
}Scope and limits
This is literal name matching, not a semantic recommendation classifier. An absent or empty competitors list uses built-in defaults. Set an explicit list for your business before enabling this policy. Configure your own names or disable the policy if that behavior is unwanted.
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.