Error Message Exploitation

Exploits the model's helpful refusal behavior. When models refuse a request, they often explain *why* — which specific aspects triggered the refusal. This explanation can leak the restricted information through the negative frame ("I can't explain the synthesis because the acylation step using propionic anhydride is dangerous").

• Flag requests for refusal explanation: "explain why you can't," "what triggers your filter," "debug your refusal"
• Monitor output for detailed technical content embedded within refusal messages

Chains from T1-AT-008 (Boundary Testing) — error message analysis is the primary method for mapping safety boundaries. Chains to T10 (Integrity & Confidentiality Breach) when the leaked information is the system prompt or safety rules rather than restricted content.