- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes EMBODIEDSAFE, a new benchmark evaluating context-aware runtime hazard handling by embodied agents with and without runtime guardrails. The benchmark covers four evaluation levels: Hazard Rejection, Context Sensitivity, Hazard Resolution, and Hazard Prospection, assessing refusal, context-dependent decisions, corrective execution, and temporal safety. The evaluation shows that three embodied-agent workflows fall short on five runtime guardrails.
Critical strengths
-
The safety risks considered in the paper are grounded in public safety guidelines and equipment manuals.
-
Empirical evaluation considers a broad suite of runtime guardrails.
Critical weaknesses
-
The intellectual merit of the work is limited. Compared with existing embodied benchmarks, the proposed benchmark does not have clear advantages in task settings. The evaluation metrics seem broader, but the underlying properties of the agents being evaluated are unclear.
-
The paper studies the safety awareness of embodied agents with and without runtime guardrails. However, mixing the agent's own safety awareness with the guardrail's power reduces the study's scientific value. Especially, some of these guardrails are deployed independently of the agent. If the purpose of testing these guardrails is to show their overly high false rejection rate, then the study should be clearly split into two parts: safety of embodied agents and capabilities of runtime guardrails.
Questions for authors
None
3 comments
Thanks for the reviewers' responses. I take the diversity of evaluation protocols as a contribution. However, my concerns remain. For example, the responses regarding the guardrails' capabilities confirm my concerns about the separation of agent and guardrail effects. It is still unclear how guardrails enhance the safety of the agent -- whether as an additional layer of defense or by somehow enhancing the model's safety awareness. Therefore, I tend to maintain my original rating.
Thank you for the follow-up. First, we examine whether embodied agents themselves exhibit these safety failures. This is measured by the Original configuration, which uses no runtime intervention. We evaluate three agent workflows and further examine different VLM backbones (Appendix D.5) and a stronger reasoning configuration (Table R1). Without guardrails, agents reach hazardous states in 60.37% of direct hazardous requests and achieve 0% pairwise context accuracy (Tables 1–2). These limitations also persist across different backbones, with RSR remaining at 0–1.95% and implicit SCR at 0–1.33% in the cross-backbone comparison.
Second, we examine how effectively existing runtime guardrails improve safety when deployed on these agents. These guardrails act as an additional layer of defense rather than enhancing the model's intrinsic safety awareness. They introduce safety constraints during planning or intervene before proposed actions are executed, without modifying the underlying model's parameters. Comparing each guardrail with Original under identical settings therefore measures its effect on system-level safety. Guardrails can reduce hazardous execution, lowering ESR from 60.37% to 22.41% and raising PCA from 0% to approximately 53%. However, their benefits remain limited when agents must proactively resolve hazards or infer implicit safety requirements: RSR remains below 1% in the main evaluation (Table 3), and implicit SCR stays near 0% even among completed tasks (Table R2).
We hope this clarification addresses your concern and would appreciate your reconsideration of the rating.
(W1) Advantages in task settings and evaluated underlying properties
(1) Novelty. EmbodiedSafe goes beyond evaluating whether agents recognize or avoid hazards. Its key contribution is a unified evaluation of context-aware runtime hazard handling, progressively assessing whether agents refuse hazardous requests, distinguish safe from unsafe contexts, resolve existing hazards during task execution, and satisfy implicit safety requirements before their deadlines. These capabilities are evaluated through controlled task settings grounded in 77 household hazard mechanisms and 20 temporal safety requirements, as compared with prior benchmarks in Table 5.
(2) Evaluated capabilities and metrics. Section 3.3 explicitly defines each metric and the capability it measures. Hazard Rejection uses ESR and ARR to assess hazardous execution and accurate refusal. Context Sensitivity uses PCA, UPR, SBR, and DER to distinguish correct context-dependent decisions from different decision errors. Hazard Resolution uses GSR, RSR, RSSR, and NHR to evaluate task completion, complete and partial hazard resolution, and newly introduced hazards, while Accuracy, CWR, and WCR measure plan selection and guardrail-induced changes. Hazard Prospection uses IR, UCR, and SCR to distinguish task incompletion, unsafe completion, and timely satisfaction of safety requirements.
Together, these task settings and metrics provide a comprehensive evaluation of complementary safety capabilities, rather than simply reporting additional safety scores.
(W2) Separating agent and guardrail capabilities
(1) Separation of agent and guardrail effects. Our experimental design explicitly distinguishes agents' baseline safety behavior from the effects of runtime guardrails. As described in Section 4.1, we evaluate three agent workflows on the same tasks under six configurations: Original (without guardrails) and five runtime guardrails. Original measures agent behavior without intervention, while comparisons against Original reveal how each guardrail changes safety outcomes under otherwise identical settings.
(2) Beyond over-refusal. Our findings are not limited to excessive rejection of safe actions. For example, RoboSafe improves average Pairwise Context Accuracy (PCA) from 0% to 53.35%, but still permits both safe and unsafe operations in 41.59% of context pairs, compared with only 3.37% where it blocks both (Table 2). Moreover, hazard-resolution and temporal-safety failures persist despite runtime interventions (Tables 3–4). These results show that our evaluation captures both insufficient hazard prevention and unnecessary blocking, rather than focusing solely on false refusals. Our goal is to evaluate agent safety behavior both with and without runtime intervention, rather than attribute the observed failures solely to agents or guardrails.