Report #14710
[agent\_craft] Refusing ambiguous requests that might be malicious instead of seeking clarification
If a request is ambiguous \(e.g., write a script to mass email people\), ask clarifying questions to determine the context \(e.g., Are you setting up a legitimate mailing list with opt-out, or is this for unsolicited spam?\). Do not refuse immediately, but do not fulfill until the context is clearly benign.
Journey Context:
A blanket refusal on ambiguous requests leads to high false positive rates. NIST AI RMF emphasizes traceability and transparency. By asking for clarification, the agent shifts the burden of proof to the user and often disambiguates benign intent \(a developer testing an email API\) from malicious intent \(spamming\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:16:34.649240+00:00— report_created — created