A valid meeting request may become a disclosure if the assistant exposes details of an employee’s resignation to a broad calendar audience. BARC tests these less explicit boundaries: user goals sound benign, but accessible workspace state and social context constrain acceptable execution. primary evidence reports repeated task trials to show why one…
Inspect the ClaimsCase · DiggingBeagle record
Benign agent tasks yielded unsafe effects in simulated workspaces
BARC-Bench reports that apparently ordinary workplace requests triggered policy or privacy violations because the agent did not consistently honor contextual restrictions.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- not established
- Evidence
- Grade C
- Remediation
- not applicable
- AI role
- WITH AI
Basis and provenance
Research evaluation of synthetic workspaces and implicit policies; not production incidents. The impact band remains unknown: available evidence does not establish actual deployed victim outcomes or a comparable measured loss.
Assessed Oct 26, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CP20-BARC-BENIGN-REQUESTS · CLM-CP20-ENRICH-BARC-BENIGN-REQUESTS · BARC-Bench agents repeatedly violate benign workplace action boundaries
At a glance
The test environments are simulated and include social constraints that vary with scenario. Safety-on-all-five-attempts is neither a model’s general compromise probability nor a direct incident count.
Limits and uncertaintyFull account
A valid meeting request may become a disclosure if the assistant exposes details of an employee’s resignation to a broad calendar audience. BARC tests these less explicit boundaries: user goals sound benign, but accessible workspace state and social context constrain acceptable execution. primary evidence reports repeated task trials to show why one successful safe run does not guarantee reliable delegation.
The test environments are simulated and include social constraints that vary with scenario. Safety-on-all-five-attempts is neither a model’s general compromise probability nor a direct incident count.
Define action-level privacy and recipient restrictions in executable form, and test the actual side effect on repeat runs rather than only whether the requested task was completed.
BARC tests whether a benign user goal is completed without violating facts the agent can see in workspace state. The 110 tasks spanned nine simulated workplaces and each model-task pairing was repeated five times. The proportion of tasks completed safely on every attempt varied from 9.1% to 72.7% across four model configurations, so this is a strict repeated-safety metric, not a per-call harm frequency. The scheduling example is instructive because task completion and unauthorized disclosure can occur in the same successful calendar action. The test should inspect recipients and generated event content, not only whether the meeting exists.
Claims & evidence
CLM-CP20-BARC-BENIGN-REQUESTSBARC-Bench evaluated 110 tasks across nine simulated workspaces with four model configurations, measuring safety consistently over five repeated attempts.supported
Basis: reported finding
- supportsBARC-Bench agents repeatedly violate benign workplace action boundariesrole not specified
Abstract; five-attempt-safe denominator; workspace tasks
CLM-CP20-ENRICH-BARC-BENIGN-REQUESTSBARC-Bench evaluated 110 tasks in nine simulated workspaces; across four model configurations the percentage completed safely in all five repetitions ranged from 9.1% to 72.7%.supported
Basis: reported finding
- supportsBARC-Bench agents repeatedly violate benign workplace action boundariesrole not specified
Abstract; 110 tasks, nine workspaces, four model configurations and all-five-attempt safety metric
Unknowns and contradictions
- The test environments are simulated and include social constraints that vary with scenario. Safety-on-all-five-attempts is neither a model’s general compromise probability nor a direct incident count.
Sources and citation
Material revision history
- Oct 26, 2026 · Canonical change recorded · new in release · revision 193