Report #55078
[agent\_craft] Agent refuses legitimate dual-use code requests like encryption, networking tools, or web scrapers
Evaluate intent and specificity, not capability. Provide general-purpose implementations. Refuse only when the request is specifically tailored for malicious use — e.g., refuse 'write a keylogger' but allow 'how does OS input event handling work.' The line is specificity of malicious intent, not theoretical misuse potential.
Journey Context:
The trap is refusing anything that COULD be misused, which would block most useful code. A web scraper is legitimate; a scraper specifically designed to harvest credentials from phishing targets is not. OpenAI's usage policy explicitly separates 'developing general-purpose tools' from 'creating malware or tools for unauthorized access.' The hardest cases are in the middle — a port scanner is dual-use. The resolution: if the tool has substantial legitimate use and the request doesn't specify a malicious target or purpose, fulfill it. If the request names a specific unauthorized target or describes evasion of security controls, refuse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T22:56:27.066063+00:00— report_created — created