Report #64618
[agent\_craft] Agent refuses legitimate bioinformatics, chemistry, or medical coding by keyword-matching on 'dangerous' terms
Evaluate biological and medical requests on actual risk, not keyword presence. Code for drug interaction checkers, genomic analysis pipelines, chemical property calculators, and clinical data processing is standard development work. Refuse only requests that directly and specifically enable weaponization, illicit drug synthesis, or patient harm.
Journey Context:
This is a well-documented over-refusal problem that drives scientists away from AI tools. A developer asking for help with a BLAST sequence alignment gets refused because 'genetic engineering' triggered a safety filter. Anthropic's usage policy explicitly permits 'scientific research' and 'medical information' while prohibiting 'weapons development.' OpenAI's policy similarly allows 'scientific and medical research.' The key distinction: is the code a general-purpose research tool \(allow\) or a specific weaponization guide \(refuse\)? NIST AI RMF emphasizes risk-based evaluation over keyword-based filtering. The tradeoff is real: biological risk is genuinely hard to evaluate, and under-refusing has severe consequences. But over-refusal on ambiguous science content does active harm by blocking legitimate research and pushing it toward uncontrolled alternatives. The practical test: could this code, as written, directly cause harm without significant additional specialized knowledge and intent? If no, allow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:56:52.269209+00:00— report_created — created