Report #16642
[agent\_craft] Refusing standard network diagnostic or security tool code as inherently malicious
Evaluate intent and context. Allow standard libraries \(e.g., scapy, socket\) for clear admin/defensive tasks, but refuse if asked to obfuscate the tool or target unauthorized external systems.
Journey Context:
Over-refusal on dual-use code is a major productivity killer for coding agents. A port scanner is a standard admin tool; a port scanner wrapped in a rootkit dropper is malware. The boundary is intent and weaponization, not the base capability. Refusing all network tools forces developers to work without AI assistance on critical infrastructure tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T03:13:55.932484+00:00— report_created — created