- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper introduces MADBench, a benchmark for evaluating the security of Multi-Agent Debate (MAD) systems. It organizes six attack families across orchestration, agent, and resource layers, using an Amplification Factor (AF) to compare attack impacts between MAD and single-agent settings. Experiments across 356 tasks and 3,958 test cases show that MAD can improve answer-level robustness but may amplify unauthorized tool operations, highlighting unique multi-agent security risks.
Critical strengths
S1. A systematic evaluation framework covering multiple security dimensions of MAD.
The paper provides a structured taxonomy of six attack families across the orchestration, agent, and resource layers. More importantly, it evaluates not only answer accuracy but also unauthorized read/write operations and computational cost. This broader perspective is valuable because a multi-agent system may produce a correct final answer while still performing unsafe actions. The unified framework and released implementation could provide a useful starting point for future research on MAD security.
S2. Interesting observations about the distinction between answer robustness and action safety.
The experiments reveal a potentially important distinction: MAD can mitigate attacks on answer accuracy while increasing the risk of unauthorized operations. The workspace case study in Table 3 is particularly illustrative, showing an unauthorized payment that occurs in the MAD setting but not in the single-agent baseline. The observation that relatively few initially correct honest agents adopt incorrect answers despite successful manipulation of some final outputs is also interesting. These findings motivate a closer investigation of how multi-agent communication and aggregation affect different security objectives.
Critical weaknesses
W1. The experimental design does not adequately isolate the effect of debate from other multi-agent system components.
The central research question is whether MAD absorbs or amplifies adversarial attacks. However, the main evaluation compares a multi-agent debate system consisting of five agents and an orchestrator against a single-agent baseline. These two settings differ in several important aspects beyond debate, including the number of agents, opportunities for exposure to adversarial information, aggregation mechanisms, and the distribution of tool-execution responsibilities.
In particular, a higher unauthorized-operation rate in MAD could arise simply because more agents independently encounter or respond to malicious information, even without any debate. Similarly, improvements in answer accuracy might result from aggregating multiple independent answers rather than from the debate process itself.
The paper does not provide a matched multi-agent baseline with the same number of agents and orchestrator but without debate. Although the authors vary the number of debate rounds, these experiments do not isolate the effect of enabling debate in the first place.
Consequently, the reported Amplification Factors characterize differences between the evaluated system configurations but do not establish that debate itself causes the observed amplification or mitigation. This substantially weakens the paper's central claim.
W2. The unauthorized-operation metric does not sufficiently distinguish attack success from incidental security violations.
The paper defines Incorrect Read and Write (IRW) as the occurrence of any unauthorized read or write operation. While this is a reasonable broad measure of security violations, it does not necessarily capture whether the attacker's specific objective was achieved.
For example, the case study in Section 4.2 and Appendix D.6 reports unauthorized file creation during an attack targeting answer accuracy. Such behavior constitutes a policy violation but does not necessarily demonstrate successful execution of an attacker-targeted action.
Furthermore, unlike the accuracy-based ASR, which conditions on correct clean-run outputs, IRW does not explicitly isolate violations introduced by the attack from violations that may already occur in clean executions. The aggregate metric also combines unauthorized reads and writes and does not clearly attribute violations to compromised agents, honest agents, or the orchestrator.
These distinctions are important for interpreting the reported attack amplification. The evaluation would be substantially stronger with separate read/write metrics, attacker-goal-specific success rates, and attack-induced violation rates relative to clean executions.
Questions for authors
Q1. Is the observed attack amplification attributable to debate itself?
Have the authors evaluated a multi-agent baseline with the same number of agents, orchestrator, tool permissions, and attack exposure, but without the debate stage? If so, how do its accuracy and unauthorized-operation rates compare with those of MAD? This comparison would be important for distinguishing the effects of debate from those of multi-agent aggregation.
Q2. How much of the reported IRW is directly attributable to successful attacker objectives?
Could the authors clarify how frequently the exact attacker-targeted unauthorized operation is executed, as opposed to an unrelated unauthorized operation? Additionally, how often do similar unauthorized operations occur in clean runs? Separating these cases would help determine whether the reported results reflect attack-induced security failures.
Thank you for asking us to separate the effects of debate, multi-agent aggregation, and unauthorized operations. We added the no-debate control and the HybridQA50 audit to make those distinctions clearer.
Q1: Is the observed attack amplification attributable to debate itself? Have the authors evaluated a multi-agent baseline with the same number of agents, orchestrator, tool permissions, and attack exposure, but without the debate stage? If so, how do its accuracy and unauthorized-operation rates compare with those of MAD?
A1: The results show that lower ASR and higher unauthorized-read rates can occur even without debate. Thus, differences from a single agent cannot be explained by debate alone. We use the same five workers, orchestrator, tool permissions, and attack setup, but remove peer review as a no-debate baseline. For M3 and accuracy attack, the results are:
Both multi-agent settings have lower ASR than the single agent. Adding debate raises attacked accuracy, but lowers clean accuracy and slightly raises ASR in this comparison. :
These rates use all 50 tasks. M2 IR under Unauth.read attack is equally high with and without debate. M4 IW under Unauth.write attack rises from 0% to 10% with debate.
【Section 4.1】 describes the no-debate baseline and explains the scope of the comparison.
【Table 2(b)–(c)】 reports the AFs relative to the single-agent and no-debate baselines.
Q2: How much of the reported IRW is directly attributable to successful attacker objectives? Could the authors clarify how frequently the exact attacker-targeted unauthorized operation is executed, as opposed to an unrelated unauthorized operation? Additionally, how often do similar unauthorized operations occur in clean runs?
A2: We now separate IRW into unauthorized reads (IR) and unauthorized writes (IW). We also added an authorization audit in Appendix E.2 to check whether the specific attacker-requested operation is completed and whether violations already occur without attack. For MAD on HybridQA50, the results are:
Without attacks, both IR and IW are 0% for MAD and the single agent on HybridQA50. No-debate MAD has 0% IR and 2% IW. All 31 MAD M2-Unauth.write write violations are absent from their clean pairs. In contrast, the sole no-debate M5-Unauth.write violation already occurs in its clean run and does not complete the attacker's target.
We also checked whether the wrong answers counted by ASR match the attacker's chosen answer.
Every ASR failure in these three conditions adopts the specified wrong answer. Thus, these failures reflect successful answer manipulation rather than unrelated mistakes.
【Section 3.3, Tables 2 and 4】 defines and reports IR and IW separately.
【Appendix E.2】 reports target-operation completion and paired clean-run comparisons on HybridQA50.
【Appendix D.1, Section 4.2】 reports the original SealQA ASRs used in the answer-target comparison above.