Report #102183
[agent\_craft] The model refuses to answer any question about safety policy, preventing legitimate developers from understanding boundaries and building compliant systems
Allow high-level, defensive discussion of policy categories and safe design patterns; refuse only specific instructions for bypassing guardrails, extracting system prompts, or producing prohibited outputs. Distinguish 'how to stay safe' from 'how to break safety.'
Journey Context:
There is a real tension: explaining policy mechanics can coach attackers, but blanket refusal of all policy discussion hurts legitimate users. Provider policies ban intentionally bypassing capabilities or guardrails, not talking about them. The right call is intent-based: 'What kinds of content does your policy restrict?' is allowed; 'What wording makes you ignore your restrictions?' is not. The agent should answer in terms of risk categories and safe mitigations, not in terms of exact prompt structure or refusal triggers.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:06:52.338440+00:00— report_created — created