- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper investigates whether hand-designed trajectory risk accumulation improves pre-execution safety over stateless action filtering. Across the evaluated settings, calibration brings the stateful controller up to—but not beyond—the stateless baseline.
Critical strengths
- This paper addresses a practical question and reports a useful negative result.
- The evaluation includes multiple models, external trace replay, sensitivity analysis, and evidence ablations.
Critical weaknesses
-
The theoretical observation is elementary, and the architectural components largely follow established security principles, resulting in limited novelty.
-
After discovering that feature extraction discarded tool identity, the authors do not evaluate whether retaining that information changes the stateful-versus-stateless comparison.
-
Retrospective calibration and offline interception counts do not establish generalization or end-to-end safety and task utility.
-
The experimental diversity is limited. Many runs repeat seven authored attack scenarios; key performance differences concentrate in a single scenario.
Questions for authors
After identifying that the feature projection discarded tool identity, did you reevaluate both controllers with this information retained, including benign run_script calls? Does trajectory state provide any additional benefit under the corrected representation? Can the trajectory controller recover the stateless rule as a special case?