- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper introduces IoD-Auditor, a framework for offline safety auditing of LLM-agent trajectories. It combines selective escalation, based on trajectory length and direct-audit confidence, with a TRACE-based multi-stage investigation pipeline. The investigation maintains a structured behavioral-evidence record covering authorization, action stages, supporting evidence, counterevidence, and defenses to guide further inspection and final adjudication. The paper evaluates the framework on four trajectory-safety benchmarks and reports improved classification performance over the evaluated baselines, together with fewer model calls than investigating every trajectory.
Critical strengths
-
Relevant problem and sensible motivation. Trajectory-level safety auditing is an important problem for tool-using agents. The paper identifies a useful tension: one-pass judgments may overlook distributed evidence, while additional investigation can amplify unsupported suspicions and introduce false positives.
-
Explicit attention to evidence and counterevidence. Separating authorization, attempted versus realized behavior, and the timing and effectiveness of defenses is a practically meaningful design choice. Requiring investigators to consider counterevidence is particularly appropriate for avoiding the conflation of suspicious behavior with established violations.
-
Evaluation includes several useful controls. Beyond comparisons across four benchmarks, the paper includes random allocation at matched call budgets, routing and protocol ablations, and adjudicator-model comparisons. These experiments address relevant questions about investigation allocation and the sources of performance differences, although the concerns noted above limit the conclusions that can currently be drawn.
Critical weaknesses
-
Limited technical contribution and insufficient novelty. The core investigation pipeline is explicitly inherited from TRACE’s Triage–Inspect–Judge framework; adaptive inspection and cross-step evidence aggregation are therefore not new contributions of this paper. The additions primarily consist of threshold-based routing using trajectory length and self-reported confidence, along with prompt instructions to record authorization, behavioral stages, counterevidence, and defenses. Although practically reasonable, these additions appear closer to heuristic scheduling and auditing-prompt refinements than a substantially new algorithm or reasoning mechanism. The budget-constrained objective is not accompanied by an optimization procedure, and the evidence-qualification predicate is primarily implemented through natural-language instructions. The paper therefore does not establish a sufficiently substantive methodological contribution beyond the existing framework.
-
Missing simple but essential baselines leave the necessity of the investigation framework unproven. The paper does not compare against repeated independent audits with majority voting or single-agent iterative review using the same evidence checklist. The Ensemble-OR/AND baselines in Table 6 combine the direct and investigation branches and do not substitute for these comparisons. Moreover, IoD-Auditor uses more calls than TRACE on several datasets, while Appendix C.3 shows that changing the adjudicating model alone can alter F1 by approximately 11–14 points. Comparisons with matched models and actual inference budgets are needed to determine whether the gains come from the proposed evidence protocol and coordination structure, rather than additional computation, more detailed prompts, or adjudicator selection.
-
The efficiency evaluation is incomplete and does not adequately support the central cost claims. Cost is measured primarily through model-call counts, despite differences in model choice and context length across roles. These calls are not equivalent units of actual expenditure. The paper does not report input/output token consumption, monetary cost, end-to-end latency, or throughput. In particular, controller–inspector interactions introduce sequential dependencies, whereas independent audits can potentially run in parallel; equal call counts therefore do not imply comparable response times. The paper also lacks performance–cost–latency comparisons with specialized safety judges or guard systems. Although their task settings may differ from offline trajectory auditing, appropriately adapted comparisons under clearly specified information-access conditions are needed to establish practical value.
-
Important numerical inconsistencies undermine confidence in the evaluation. Table 4 reports 450 unsafe and 90 safe TraceSafe trajectories, whereas Table 2 reports 100% precision, 34.4% recall, and 67.2% accuracy for Full-GLM. Under the stated unsafe-class evaluation, the reported precision and recall imply approximately 45.3% accuracy on that class distribution, not 67.2%. The full-system F1 scores also differ substantially between Tables 2 and 3: 79.3 versus 73.1 on TraceSafe and 67.0 versus 71.7 on MCPHunt. The authors need to specify the evaluation samples, aggregation procedures, and run configurations for each experiment and provide confusion matrices. These discrepancies cannot be explained by ordinary rounding, and the principal results cannot currently be reconciled.
-
The length-stratified results conflict with the stated routing policy. According to Section 4.2 and the implementation details, every trajectory with at least four steps is routed directly to investigation. Under matched configurations, IoD-Auditor and All-Investigate should therefore execute the same investigation branch on these trajectories. Nevertheless, Figure 4 shows substantial differences in call counts for length groups entirely above this threshold, including approximately 11 versus 19 calls in the six-to-ten-step group. Independent stochastic runs may introduce variation, but these differences cannot simply be attributed to selective routing when the routing decisions are identical. The authors need to clarify whether different internal budgets, implementations, or experimental configurations were used; otherwise, these results do not support the proposed explanation for the efficiency gains.
-
The evaluation does not directly validate the claimed reasoning benefits of the evidence protocol. In Table 8, evidence qualification reduces false-positive rates but also lowers recall. On ATBench500, for example, recall decreases from 96.34% to 92.68% relative to “No qualification,” while F1 remains unchanged at 89.94%. This result is also consistent with a more conservative decision policy and does not, by itself, establish more accurate interpretation of behavioral evidence. Comparisons at matched recall are needed, together with independent evaluation of evidence-citation correctness, behavioral-stage identification, and defense-effectiveness assessment. The current trajectory-level classification metrics do not directly validate these capabilities, despite their central role in the claimed contribution.
Questions for authors
see weaknesses.