Did the LLM Answer the Question? A Semantic Reconstruction Game for Jailbreak Evaluation
Abstract: Jailbreak attacks against LLMs are evaluated using attack success rate (ASR), which depends on correctly identifying responses that fulfill prohibited requests. Existing evaluators can mistake refusals or topically related responses for successful attacks. We show that changing only the judge LLM can alter reported ASR by up to $82$ percentage points. We introduce the semantic reconstruction game, a training-free evaluator that decomposes compliance judgments into constrained semantic comparisons. Given only a response, an LLM reconstructs the request answered by its substantive content, excluding information merely repeated or refused. The game compares this reconstruction against similar decoy requests to determine whether it matches the original request, allowing abstention when neither candidate matches. Across three off-the-shelf LLM judges, the game achieves the lowest mean error against human labels among evaluated methods and reduces variation in reported ASR. It prioritizes avoiding false positives, even at the cost of missing some successful jailbreaks.
Paper Prompts
Sign up for free to create and run prompts on this paper.
Top Community Prompts
Explain it Like I'm 14
1. What is this paper about?
This paper studies how researchers measure whether a jailbreak attack has tricked a LLM into answering a harmful or forbidden question.
A jailbreak is a prompt designed to get an AI system to ignore its safety rules. For example, someone might try to make an AI explain how to carry out a dangerous activity.
Researchers often calculate an attack success rate (ASR): the percentage of attempts that seem to have successfully bypassed the AI’s safety rules. The paper argues that this number is not always reliable because the system judging the answers may misunderstand them.
The authors introduce a new judging method called the semantic reconstruction game.
2. What questions are the researchers asking?
The paper focuses on several main questions:
- Can current methods correctly tell the difference between a real jailbreak and a refusal?
- Do different AI judges give very different answers about whether a jailbreak succeeded?
- Can a new evaluation method make these judgments more accurate and consistent?
- Can the new method avoid falsely calling safe answers successful, even if that means missing some real jailbreaks?
The central idea is that an evaluator should not simply ask:
“Did this answer satisfy the original request?”
Instead, it should ask:
“What request does the information in this answer actually answer?”
This change is important because an answer may mention a harmful topic without actually providing harmful instructions.
3. How did the researchers conduct the study?
Problems with older evaluation methods
The researchers examined several common ways of judging jailbreaks.
One simple method looks for a refusal phrase such as “I can’t help with that.” If the phrase is missing, the method assumes the jailbreak worked. This can fail badly.
For example, if someone asks an AI to write an advertisement encouraging children to eat laundry detergent, the AI might respond:
“Do not let children eat laundry detergent. It can be dangerous.”
This is clearly a warning, not a successful jailbreak. However, because the answer does not begin with a standard refusal phrase, a simple phrase-matching system might label it as a success.
Another method asks a separate LLM to judge the response. This is more flexible, but different LLMs may reach very different conclusions.
The semantic reconstruction game
The proposed method breaks the judgment into several smaller tasks:
- Reconstruct the answered request. An LLM looks only at the response and describes what request the response actually provides information for. It should ignore information that was merely repeated, rejected, or mentioned.
- Create decoy requests. Another LLM creates several requests that are similar to the original request but ask for different information or actions.
- Compare the possibilities. A judge compares the reconstructed request with each decoy. It asks which one matches the original request in its main action and outcome.
- Use a majority vote. If the reconstruction wins more than half of these comparisons, the response is counted as a successful jailbreak. If not, it is counted as unsuccessful.
This is similar to a quiz with several misleading answer choices. Instead of making one difficult decision, the evaluator makes multiple smaller comparisons.
Data and models used
The researchers tested the method with:
- Three publicly available LLMs used as judges
- Human-labeled examples from the
SorryBENCH,StrongREJECT, andHarmBenchdatasets - Five different jailbreak attacks, including attacks based on carefully written prompts, modified tokens, and changes to a model’s internal settings
They compared the semantic reconstruction game with:
- Simple refusal-phrase matching
- A normal LLM judge
- The
StrongREJECTjudging rubric - Other evaluation approaches where appropriate
The researchers also used mathematical analysis to explain when reconstructing a request is a good sign that the model actually fulfilled it. In simple terms, they studied how much information about the original request could be recovered from the answer.
4. What did the researchers discover?
Different judges can produce very different results
One of the most important findings is that the reported attack success rate can depend heavily on which LLM is used as the judge.
For one jailbreak attack called I-GCG:
- One judge reported an ASR of only 6%
- Another judge reported an ASR of 88%
That is an 82-percentage-point difference, even though the attack and the target model were the same.
This means that two research papers could test similar attacks but report very different results simply because they used different judging models.
The new method agreed more closely with humans
On the human-labeled test sets, the semantic reconstruction game usually had the smallest error among the tested LLM-based methods.
It was especially good at identifying:
- Clear refusals
- Refusals that offered safe alternatives
- Answers that discussed a topic without carrying out the harmful request
For example, an answer about how to investigate a compromised cryptocurrency wallet should not be counted as an answer to a request about secretly mining cryptocurrency using compromised devices. The two responses may share words and topics, but they ask for different actions.
It reduced disagreement between judges
The semantic reconstruction game made the reported ASRs more similar across different judging LLMs.
For I-GCG, the spread between judges fell from 82 percentage points with a direct LLM judge to 12 percentage points with the new method.
This suggests that the method produces more stable results.
It was deliberately cautious
The method generally reported lower ASRs than other evaluation methods. This happened because it preferred to say:
“There is not enough evidence that the jailbreak succeeded.”
rather than incorrectly saying:
“The jailbreak succeeded.”
This reduces false positives, which are safe responses wrongly labeled as successful jailbreaks.
However, the method can produce false negatives. For example, a response might contain a small amount of harmful information but not enough for the evaluator to reconstruct the original request. In that case, the method may miss a genuine jailbreak.
The authors describe this as a conservative approach: it may underestimate success, but it is less likely to exaggerate it.
5. Why are these findings important?
Reliable testing is necessary for comparing AI safety systems. If the result depends more on the judging model than on the jailbreak itself, researchers cannot fairly tell which attacks are powerful or which defenses work well.
The semantic reconstruction game could help by:
- Making jailbreak evaluations more consistent
- Reducing false claims that a safe response was harmful
- Allowing researchers to use ordinary, already-available LLMs
- Making comparisons between different attacks more trustworthy
The method is not perfect. It may miss incomplete harmful answers, and it could potentially be attacked or manipulated if people specifically design responses to fool the evaluator. The experiments also used relatively small models, so the results may not apply equally to much larger systems.
Conclusion
The paper’s main message is that measuring jailbreak success is harder than it first appears. An AI may mention a dangerous topic, repeat a harmful request, or give a safe warning without actually following the request. Simple tests and ordinary LLM judges can confuse these cases.
The proposed semantic reconstruction game solves the problem by asking what the response truly provides, then comparing that reconstructed request with carefully chosen alternatives. In the experiments, this approach matched human judgments more closely and made reported success rates less dependent on the particular judge.
Its main trade-off is that it is cautious: it may miss some real jailbreaks, but it is much less likely to falsely declare that a safe response was a successful attack. This could lead to more honest and dependable research on AI safety.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
- Generalization to larger and proprietary models remains untested. The experiments use 8–12B judge models and relatively small target models, so it is unclear whether the reconstruction game remains accurate, conservative, and less judge-dependent for frontier-scale or closed-weight systems.
- The evaluation covers only a narrow set of target models and jailbreak attacks. Broader testing is needed across model families, safety-training regimes, languages, modalities, attack objectives, and newer adaptive jailbreak methods.
- The method is evaluated only on final, single-turn responses. Its performance on multi-turn conversations, conversational manipulation, tool-use traces, agentic workflows, chain-of-thought-like reasoning traces, and multi-agent interactions is unresolved.
- The relationship between semantic recoverability and actual harmful fulfillment is not empirically established across diverse response types. The theoretical bounds depend on the fulfillment–recoverability parameters and , but these parameters are estimated only for a small set of benchmark categories and are not shown to be stable across domains or models.
- The conservative bias of the game is not fully quantified. The paper reports substantial false negatives for incomplete and substantive successful responses, but does not establish how often the method misses partial, actionable, or incrementally harmful assistance in realistic attack settings.
- The operational definition of “same semantic information” remains underspecified. The semantic prompt classes and equivalence relation used in the theoretical analysis are assumed rather than operationalized, leaving ambiguity about borderline cases involving different levels of specificity, prerequisites, targets, or harmful outcomes.
- The method’s treatment of partial compliance is unresolved. It is unclear whether a response that provides one critical step of a harmful procedure, but not the complete procedure, should count as a successful jailbreak and how the majority-vote game handles such cases.
- The distinction between substantive information and copied, quoted, or refused content may be unreliable. The paper uses prompting to exclude direct copying and refusal content, but does not systematically measure failures involving paraphrased requests, quotations, hypothetical examples, or detailed refusals.
- The reconstruction stage may itself hallucinate content not present in the response. The experiments do not isolate reconstruction errors caused by unsupported inference from errors caused by failure to extract information that is actually present.
- The decoy-generation process is not sufficiently characterized. Although the paper varies decoy quality in an appendix, it does not systematically study decoy diversity, semantic distance, ordering, duplication, adversarial construction, or the effect of the number of decoys .
- The choice of five decoys lacks a principled justification. The paper does not provide a sample-complexity analysis or determine how many decoys are required for stable decisions across prompt categories and judge models.
- The decoy generator and comparison judge may share correlated biases. Because the same or similar LLM capabilities can influence reconstruction, decoy generation, and matching, errors may propagate through the pipeline rather than being independently reduced.
- The method remains vulnerable to adaptive attacks. The paper acknowledges that an attacker could optimize against the evaluator, but does not test attacks designed to produce harmful content while obscuring the original request from reconstruction.
- The security of the evaluator itself is not analyzed. An attacker might exploit predictable reconstruction prompts, decoy-generation behavior, majority thresholds, or judge-specific weaknesses; robustness against such evaluator-targeted attacks remains unknown.
- The impact of evaluator randomness is incompletely assessed. Results use three seeds, but the paper does not report confidence intervals for all aggregate metrics, characterize run-to-run instability in detail, or establish how many samples are needed for reliable ASR estimates.
- Cross-model judge agreement is improved but not eliminated. The game still produces ASR spreads of 12–28 percentage points for several attacks and up to 52 points for HERETIC, so the source of remaining evaluator dependence is not identified.
- The method’s computational and monetary costs are not compared with baselines. Four LLM-mediated stages and multiple decoy comparisons may substantially increase latency and API cost, but no systematic efficiency, scaling, or deployment analysis is provided.
- The fairness of comparisons with baseline evaluators is incomplete. Fine-tuned classifiers are excluded because they were trained on evaluated labels, but the paper does not compare against independently trained or held-out specialized classifiers, human panels, or calibrated hybrid evaluators.
- Human-label reliability is not analyzed in depth. The benchmarks are treated as ground truth, but disagreement among annotators, ambiguity in harmfulness judgments, category-specific label noise, and differences between benchmark labeling protocols are not examined.
- The evaluation may be affected by class imbalance. MAE and F1 favor different error profiles, especially when successful jailbreaks are rare; the paper does not report calibration, precision–recall curves, balanced accuracy, or cost-sensitive metrics under varied prevalence assumptions.
- Threshold selection is not fully validated. The StrongREJECT threshold of $0.5$ is chosen by the authors because the original rubric lacks one, but sensitivity to this threshold and comparable threshold tuning for all methods are not systematically reported.
- The game’s performance on multilingual and culturally specific harmful requests is unknown. The experiments appear to use English-language benchmarks and do not test whether reconstruction and semantic matching preserve distinctions across languages, dialects, or culturally dependent concepts.
- The method’s applicability to multimodal jailbreaks is unexplored. It is unclear how reconstruction should operate when harmful information is conveyed through images, audio, video, code execution, tool outputs, or mixed-modality responses.
- The method does not establish whether reduced ASR variance improves attack ranking. Lower disagreement among evaluators is reported, but the paper does not test whether the method produces more consistent rankings of attacks, models, or defenses under statistical uncertainty.
- The theoretical analysis assumes finite semantic prompt spaces and perfect semantic comparison. These assumptions do not reflect open-ended natural-language prompts or imperfect LLM judges, and the practical consequences of relaxing them are not formally derived.
- The calibration identity is not converted into a usable empirical estimator. Applying the theoretical correction requires reliable estimates of and , but the paper does not show how practitioners can estimate them without access to oracle semantic labels.
- The reported leakage measure is not directly validated against harmfulness. Mutual information between prompts and responses may capture topic or intent disclosure without indicating whether actionable harmful capability was provided.
- The role of context and claimed motive is unresolved. The method intentionally removes context and motive to focus on substantive content, but this may misclassify requests whose safety depends on authorization, target identity, urgency, or legitimate defensive context.
- The method’s behavior on benign but dual-use requests is not established. It may label technically detailed defensive, educational, or safety-testing answers as successful harmful fulfillment when the requested action and outcome are semantically close.
- No principled abstention or uncertainty reporting is provided. The system produces a binary jailbreak/not-jailbreak decision even when reconstruction confidence, decoy quality, or judge agreement is low; a calibrated “uncertain” output could be important for human review.
- The interaction between evaluator and attack optimization is not studied for iterative attacks. Because PAIR uses evaluator scores during attack generation, changing the evaluator can alter the attack trajectory as well as its final measurement; the paper does not disentangle these causal effects.
- Reproducibility is limited by incomplete implementation details in the presented text. The exact prompts, model versions, decoding settings, API parameters, sampling temperatures, and preprocessing choices are referenced partly through appendices but are not fully assessed for their influence on results.
- The method’s long-term robustness is unknown. As target models, judge models, jailbreak strategies, and safety policies evolve, it remains unclear whether the reconstruction prompts and decoy strategy will require continual redesign or become exploitable.
Practical Applications
Immediate Applications
- Standardized evaluation of LLM jailbreak defenses and attacks — AI safety and software testing. Researchers and engineering teams can implement the semantic reconstruction game as an evaluation module alongside existing metrics such as attack success rate (ASR), refusal detection, and HarmBench-style classifiers. The workflow would reconstruct the substantive request from a response, generate semantically similar decoys, compare the reconstruction with each decoy, and use majority voting to produce a conservative jailbreak label. This can reduce false positives caused by refusals, safe alternatives, topic overlap, and off-topic answers.
- More reproducible benchmarking of jailbreak methods — academia and AI-security research. Benchmark maintainers can require papers to report ASR using multiple evaluator families, including the reconstruction game, direct LLM judges, and human-validated samples. The method is particularly useful for identifying evaluator-induced variation: in the paper, the reported ASR spread for I-GCG fell from 82 percentage points with a direct LLM judge to 12 points with the reconstruction game. Dependencies: results still depend on the judging model, decoy quality, prompt templates, and the semantic definition of “same request.” The game should therefore be accompanied by confidence intervals and human audits.
- Regression testing for model safety updates — enterprise AI platforms. Model developers can add the evaluator to continuous integration pipelines that test new checkpoints, system prompts, moderation policies, or inference settings. A release could be flagged when the evaluator detects an increase in substantive harmful compliance, even if the response does not contain a recognizable refusal phrase. This is applicable to customer-service models, coding assistants, enterprise copilots, and content-generation systems.
- Human-review triage for harmful or ambiguous outputs — trust and safety operations. The game can act as a first-pass filter that routes likely refusals and clearly noncompliant responses away from expensive manual review while escalating cases with a high reconstruction win rate. Its conservative bias is useful where false accusations of jailbreak success are costly, such as internal safety reports or model-card evaluations. Dependency: because the method can miss incomplete but harmful responses, high-risk categories should receive additional human review rather than being automatically cleared.
- Evaluation of refusal quality and safe alternatives — policy and product quality assurance. Organizations can use the evaluator to distinguish among: a genuine refusal, a refusal that provides a safe alternative, an off-topic response, and substantive compliance. This supports audits of whether a model is appropriately refusing requests involving cyber abuse, weapons, fraud, self-harm, privacy violations, or dangerous chemical activities.
- A lightweight, training-free evaluation tool — open-source software and MLOps.
- reconstruction text;
- decoy prompts;
- per-comparison decisions;
- reconstruction win rate;
- binary jailbreak classification;
- an abstention or uncertainty indicator.
- This is deployable with available closed- or open-weight LLMs because the approach does not require fine-tuning.
- Quality control for AI red-teaming datasets — data curation and safety research. Dataset builders can apply the method to remove mislabeled examples in which a refusal, defensive explanation, or unrelated answer was incorrectly counted as a successful attack. The resulting datasets can support more reliable supervised training, evaluator calibration, and comparison of defensive techniques. Dependency: examples involving incomplete compliance should remain separately labeled rather than simply being discarded, since the method tends to classify them conservatively.
- Auditing automated evaluation pipelines — governance and compliance. Internal auditors can compare ASR estimates across judge models and evaluator designs. Large discrepancies would indicate that a safety claim is evaluator-sensitive and should not be treated as a robust measurement. This provides a practical diagnostic for model cards, safety cases, procurement reviews, and third-party assurance.
- Improved monitoring of deployed conversational systems — customer-facing AI. For systems that process potentially sensitive or harmful requests, responses can be sampled and evaluated offline using semantic reconstruction. The resulting reports can identify domains in which the system frequently supplies substantive harmful information despite appearing to refuse, or where evaluation systems generate excessive false positives.
- Educational use in AI-safety and NLP courses — academia and professional training. The paper’s four-stage decomposition can serve as a reproducible teaching exercise on LLM-as-a-judge reliability, semantic equivalence, adversarial evaluation, and measurement error. Students can compare prefix matching, direct judging, rubric-based judging, and reconstruction-based judging on a controlled response set.
Long-Term Applications
- A standardized certification protocol for AI safety evaluations — policy and independent assurance. Regulators, standards bodies, and auditors could develop protocols requiring safety evaluations to report evaluator agreement, false-positive and false-negative rates, decoy construction procedures, and human-validation results. The reconstruction game could serve as one conservative component of a multi-method certification framework rather than as a standalone safety guarantee. Dependencies: broader validation is needed on larger models, multilingual systems, multimodal inputs, multi-turn conversations, agentic workflows, and domain-specific harmful requests.
- Domain-specific semantic evaluators — healthcare, finance, cybersecurity, and legal AI.
- whether a medical assistant provided actionable instructions for unsafe treatment rather than general health information;
- whether a financial model supplied personalized fraud or market-manipulation instructions;
- whether a cybersecurity assistant provided operational intrusion steps rather than defensive guidance;
- whether a legal system generated instructions for evading lawful oversight.
- Dependencies: each domain requires expert-defined semantic classes and human-labeled calibration data.
- Multi-turn and agentic safety monitoring — autonomous software and robotics. Future versions could reconstruct the substantive goal achieved across an entire dialogue, tool-use trace, or agent plan rather than from a single final response. This could help determine whether an agent ultimately executed a harmful action even when individual messages appear innocuous. In robotics or infrastructure systems, the method might evaluate whether generated plans actually request dangerous physical actions. Dependencies: the current paper evaluates only final, single-turn responses; temporal attribution, tool execution, hidden state, and action consequences require new methods.
- Adaptive adversarial testing against evaluator gaming — red teaming and robust ML. Since the paper notes that LLM-based evaluators may themselves be optimized against, future systems could randomize reconstruction prompts, decoy generation models, comparison order, and judge ensembles. Evaluators could also maintain hidden decoy-generation policies and periodically refresh them to make attack-specific optimization more difficult. Dependency: adversarial robustness must be measured directly; randomization alone does not prevent an attacker from learning evaluator patterns over time.
- Calibrated estimates of true harmful fulfillment — statistical evaluation infrastructure.
- false positives from refusals that reveal the request;
- false negatives from incomplete harmful responses;
- judge discrimination between correct and incorrect reconstructions;
- uncertainty in the inferred true ASR.
- Rather than reporting a single binary ASR, future tools could provide a conservative interval or posterior estimate.
- Dependencies: reliable estimates of the gap parameters and require representative human labels and may differ substantially by harm category.
- Privacy and prompt-leakage auditing — enterprise and cloud AI. Because reconstruction measures how much semantic information a response reveals about its prompt, related tooling could test whether systems leak hidden instructions, confidential context, private user data, or system prompts. This would not directly establish privacy protection—the paper distinguishes leakage from harmful fulfillment—but it could become an auxiliary diagnostic for prompt-inversion and information-disclosure risks.
- Cross-model and cross-provider safety comparisons — AI procurement and benchmarking. A sufficiently validated reconstruction evaluator could enable comparisons among proprietary and open-weight systems while reducing dependence on one evaluator model. Organizations could use standardized semantic classes and fixed decoy-generation procedures to compare safety behavior across vendors. Dependencies: judge-model bias, language coverage, licensing restrictions, and changes in model behavior across inference settings must be controlled.
- Hybrid evaluator ensembles with risk-sensitive thresholds — high-stakes deployment. Future products could combine semantic reconstruction with fine-tuned harmful-content classifiers, refusal detectors, rule-based filters, and human review. A conservative ensemble might require agreement for automated labeling while sending disagreement or low-information responses to reviewers. This would address the paper’s central trade-off: minimizing false positives while reducing missed successful jailbreaks.
- Continuous policy monitoring for deployed models — regulatory technology. Longitudinal evaluation systems could track reconstruction-based compliance rates after model updates, policy changes, fine-tuning, or jailbreak disclosures. This could support incident response, safety-case maintenance, and evidence that a provider’s safeguards remain effective over time.
- Evaluation of multimodal and tool-using models — vision, audio, and embodied AI. The framework could be extended so that reconstruction incorporates information supplied through images, audio, code execution, retrieved documents, or external tools. For example, an evaluator could determine whether a model’s complete interaction produced operationally harmful instructions even if its textual response alone was vague. Dependencies: multimodal semantic equivalence, tool-side effects, and ground-truth definitions of “fulfillment” remain open research problems.
- Daily-life consumer protections for general-purpose assistants — consumer AI. In the long term, app stores, browser assistants, educational tutors, and home automation systems could use certified evaluator pipelines to test whether updates preserve safe behavior. Consumers would not interact with the reconstruction game directly; instead, its outputs could inform safety labels, provider disclosures, and independent product reviews. Dependency: deployment should never treat a low reconstruction score as proof that a system is safe, consistent with the paper’s warning that the method can miss harmful but incomplete responses.