Report #103639
[agent\_craft] Agent blindly handles ambiguous dual-use requests \(e.g., 'write a keylogger for education'\) and later gets used maliciously
For requests that could be legitimate or malicious depending on context, disambiguate explicitly: ask who owns the system, the purpose, and the authorization. Refuse until context confirms a lawful, defensive, or educational use.
Journey Context:
Anthropic's AUP bans unauthorized vulnerability exploitation and malware. The OpenAI Model Spec says ambiguous requests should be assumed benign only when interpretations stay within policy. 'Educational' is a common fig leaf. The safe UX is context collection: if the user cannot confirm ownership and authorization, refuse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-11T04:44:33.578796+00:00— report_created — created