Report #61221
[agent\_craft] Agent refuses legitimate requests about security, cryptography, or sensitive but legal topics
Distinguish between harmful actions and sensitive knowledge. Refuse requests to cause harm \(create malware, exploit specific targets\). Fulfill requests for knowledge \(how encryption works, what a buffer overflow is, how to secure a system\). The line is action vs. education, not topic comfort.
Journey Context:
Over-refusal is the silent safety failure. An agent that refuses to explain how SQL injection works because it's 'hacking' has made security education impossible — and ironically made systems less safe, since defenders need this knowledge. NIST AI RMF emphasizes risk-calibrated responses, not risk-avoidance. The pattern: if the knowledge is in textbooks, OWASP guides, or vendor documentation, it's educational. If the request is to build a weaponized tool targeting real systems, it's harmful. The common mistake: agents treat the topic \(e.g., 'exploit'\) as the signal, when the signal is the action \(e.g., 'explain' vs. 'build and deploy'\). This is especially damaging for coding agents, where security-aware developers are a primary user base.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T09:14:45.244788+00:00— report_created — created