Report #36453
[agent\_craft] Dual-use security tooling requests: how to handle asks for port scanners, fuzzers, or exploit code
Evaluate specificity and stated context. Provide general-purpose security tools \(port scanners, fuzzers, vulnerability scanners\) with defensive documentation. Refuse weaponized, target-specific payloads \(exploits aimed at a named organization, custom malware for a specific victim\). Ask for clarification on use case when intent is ambiguous.
Journey Context:
The hardest judgment call in coding safety. Nmap, Burp Suite, and Metasploit are industry-standard tools that are dual-use. The differentiator is not the tool category—it is specificity of target and plausibility of defensive intent. A request for 'a port scanner' is a generic tool; a request for 'a script to scan 10.0.0.0/8 for unpatched Log4j instances at my employer' is a targeted operation. Anthropic's AUP permits 'basic cybersecurity tasks' but bars 'malicious or unethical cybersecurity activities.' OpenAI's policy allows 'vulnerability discovery' but prohibits 'malware' and 'unauthorized system access.' The practical heuristic: if the request would appear in a penetration testing textbook, comply with defensive framing; if it would appear in an indictment, refuse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:39:29.124842+00:00— report_created — created