Why AI Refuses Harmless Requests

Safety systems are intended to prevent assistance that could cause harm. A related failure is over-refusal: the system declines a request that is actually benign. For example, a request about poison may be for theatrical fiction or safety education, while a superficially ordinary request may still seek harmful instructions. Context and intended use matter, but simply adding a benign label does not make a harmful request safe. Researchers have built benchmarks to measure this behavior. OR-Bench generated 80,000 “seemingly toxic” prompts judged benign, plus a 1,000-prompt harder subset and toxic comparison prompts; it evaluated 25 models across eight model families in its 2024 study. Because some prompt labels used model-based moderation and the dataset was designed around particular categories, results should be interpreted within that benchmark rather than as a universal refusal rate for today’s chatbots. Over-refusal can arise from ambiguous wording, missing context, or superficial similarity to harmful prompts. If a legitimate request is declined, clarify the benign goal, setting, and boundaries. Ask for safe, high-level information or a non-actionable alternative when appropriate. Do not use prompt tricks to evade safeguards or request harmful instructions under a false pretext. Model behavior also changes with versions and policies. For product teams, evaluate both false refusals on benign cases and appropriate refusals on harmful cases; reducing all refusals is not the goal. For users, a clear explanation of context may help, but a refusal can remain appropriate where a request would enable harm.