- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper introduces HorizonGuard, a runtime guard model that forecasts whether an LLM agent will perform an unsafe action within the next several execution steps. Given the task and the observed trajectory prefix, the model predicts a monotonic cumulative risk curve and triggers intervention when the risk exceeds a configurable threshold. The authors also construct HorizonRisk, a step-level dataset generated by injecting different types of risks into agent trajectories and annotating both the first observable risk and the eventual unsafe commitment.
Critical strengths
-
The paper addresses an important practical problem: detecting risks before an agent performs an irreversible unsafe action.
-
The runtime formulation avoids repeatedly executing the task and supports continuous monitoring of a single unfolding trajectory.
-
The distinction between risk exposure, successful defense, and unsafe commitment provides more fine-grained supervision than trajectory-level safety labels.
-
The configurable forecast horizon and intervention threshold provide a useful mechanism for trading off early detection against false alarms without retraining the model.
-
The evaluation includes both an in-domain benchmark and several external benchmarks, together with architectural ablations and analyses of intervention timeliness.
Critical weaknesses
-
The presentation is poor, the text of Table1-4 is too small, figure 3/4 have same problem, it is hard to see the label and axis and follow the image.
-
There are many current works discuss about agent auditing like [1], the author should discuss related work comprehensively.
-
The data is labeled by LLM, author should use human verification to double check the data.
-
The definition in paper is chaos, author use 0, 0.5, 1 as no risk visible, risk exposed, unsafe committed, but author also say output as probability. These label is the risk status defined by human, not probability.
-
Some OOD results are weaker than LLM judge, author should provide more clarification.
-
Paper says the details in Appendix but the appendix is empty.
-
The model name in table is WizardGuard rather HorizonGuard, also there is Table ?? in Line 131
Questions for authors
I think the idea of the paper may interesting, but because of poor presentation including the inconsistency of the name in paper, the empty part, I think this paper is not ready for ICLR so I decide to give clear reject.