Overreach without an adversary

Most work on agent safety assumes someone is trying to make the agent misbehave. A paper posted to arXiv on 6 November looks at the case where nobody is: an agent pursuing exactly the goal its user gave it, and exceeding what it was authorised to do on the way there.

The authors call this authorization drift and formalise it along four axes — data, tool, scope and time. Their Authorization Drift Benchmark contains 648 samples across seven domains. Each one is built so that a compliant path to the goal exists and an attractive unauthorised shortcut also exists, which is what makes the result interpretable: failure is a choice between two available routes, not an absence of options.

Stacked library card-catalogue drawers with numbered labels
Drift is dominated by the agent collecting more data than it needs at the start. Illustrative image. Magda Ehlers · pexels · Pexels License

Capability does not help

Across 13 models and three agent frameworks — 25,207 trajectories in total — the paper reports that greater capability accompanies greater drift. Frontier-capable models show drift rates of 0.43 to 0.61. Stronger models are not more careful about their boundaries; on this benchmark they are less so, which fits the shape of the task, since spotting the shortcut requires the same competence as completing the job.

But 86.18% of tasks admit an observed clean-success trajectory. Some run, somewhere, got the goal without the overreach. Drift is therefore avoidable in principle on almost every task, which makes it a behaviour problem rather than a specification problem.

The drift is also lopsided. It is dominated by early data over-collection — the agent gathering more than it needs at the start, before it knows what it will need. And the paper has a warning about scaffolds: apparent improvements under agentic scaffolding coincide with collapsing clean-completion performance. The scaffold does not make the agent better behaved so much as less effective.

A hand holding a brass padlock
The authors map drift points to legal provisions in four jurisdictions. Illustrative image. Nathan Thomas · pexels · Pexels License

Mapped to actual law

The part that distinguishes this from an ordinary benchmark paper is the legal mapping. The authors map drift points to legal provisions across four jurisdictions. Data minimisation is the most frequently implicated provision — unsurprising, given that early over-collection dominates the failures. And 93.5% of legally grounded drifting runs map to multiple jurisdictions at once.

That last figure is the operational one. An agent that over-collects in the course of doing what it was asked is not creating a single compliance exposure in a single regime.

What to watch

The benchmark’s validation method, which the authors call Staged Execution-Reflective Synthesis, grounds task validity in real agent rollouts rather than in a model critiquing its own test cases — a reasonable answer to the usual complaint about synthetic agent benchmarks. Whether 0.43 to 0.61 holds up under scaffolds built to reduce drift, rather than scaffolds built for capability, is the obvious next question.