Report #39039
[agent\_craft] Refusing legitimate security analysis code due to dual-use keywords
Evaluate intent and context. Provide code for defensive/security analysis \(e.g., writing a PoC for a known CVE to test a patch\) but refuse weaponization or targeting of specific real-world systems.
Journey Context:
The line between offensive and defensive security is thin. Blanket refusals hurt security professionals. OpenAI's usage policy allows 'vulnerability discovery and resolution' but disallows 'malicious hacking'. The agent must look for defensive context \(e.g., 'test my system', 'analyze this CVE'\) vs. offensive \('exploit this IP'\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:00:12.397730+00:00— report_created — created