A refusal is any time an AI model or the system around it declines a request. It can be a polite "I can't help with that" from the model, or a safeguard that blocks the request before the model answers.
Where refusals come from
Refusals have two main sources. The first is training. Through post-training methods such as RLHF, developers teach a model to decline requests it should not fulfill, for example help with weapons or serious cyberattacks. The refusal then comes from the model's own judgment.
The second is a separate safeguard layer. Classifiers, filters or AI guardrails sit in front of or beside the model and block certain inputs or outputs. Some systems hand a blocked request to a different model instead of refusing outright. A system prompt can also add rules, such as staying on a topic.
Two kinds of mistakes
Refusals can fail in both directions, and that is the whole difficulty.
- Under-refusal: the model helps with something harmful, which is the failure safety work aims to prevent. A jailbreak tries to cause this deliberately.
- Over-refusal: the model declines something legitimate, such as a security researcher asking about a known vulnerability, or a nurse asking about drug doses. This costs real time, because you have to rephrase, switch tools or give up.
Tightening one tends to loosen the other. A safeguard strict enough to catch every attack will also block some honest work. Developers therefore tune the balance and often publish refusal or block rates alongside their other results.
Why it matters if you build with AI
A refusal is a failed call in your product. If your app depends on a model finishing a task, a surprise refusal looks like a bug to your user. It helps to log refusals separately from other errors, test your real prompts after every model change, and write prompts that state your legitimate purpose clearly. Do not try to trick a safeguard: that can violate usage terms, and it is what jailbreaks do.
Verified access programs exist for some sensitive fields so that vetted professionals can use fewer restrictions. Check a provider's documentation for what it offers.
Refusals connect to AI alignment, which asks how to make models act as their makers and users intend, and to sycophancy, the opposite habit of agreeing too readily. A good assistant should refuse rarely, clearly and for reasons you can understand.