Skip to content
aiqbench takeAI Safety

aiqbench analysis

This research proposes "Environment Steering," a runtime safety mechanism that monitors data flows within agent execution environments to intercept unsafe tool calls and guide agents toward compliant trajectories. By treating the agent's state as database tables subject to declarative policies, the approach achieves zero attack success rates while maintaining task performance, offering a robust alternative to pre-execution constraints or model-dependent judges.
Sources coveringarXiv, LessWrong, Cybersecurity News, Latent Space
What this isA model's reading of the article and related coverage, written for aiqbench. Not the publisher's words.

Environment Steering: Using Data Flow Control to Improve Agent Utility and Safety

arXiv2 min read

arXiv:2609.35807v1 Announce Type: new Abstract: LLM agents can make unsafe tool calls even when instructed to behave safely. Existing defenses constrain agents before execution, modify tool inputs/outputs, or rely on LLM judges; these approaches may depend on model behavior or block unsafe actions without helping the agent recover. We argue that the execution environment should instead enforce safety as the agent runs and steer it toward safe alternatives when violations occur---we call this Environment Steering. We implement this by modeling the agent and harness execution state as database tables, track the record-level data flows, and check these data flows against declarative policies during runtime. When violations are detected, policy- and context-specific feedback steers the agent toward safe trajectories. On AgentDyn, this enables the agent to improve task success rate over no-defense while achieving 0% attack success rate.

Abstract:LLM agents can make unsafe tool calls even when instructed to behave safely. Existing defenses constrain agents before execution, modify tool inputs/outputs, or rely on LLM judges; these approaches may depend on model behavior or block unsafe actions without helping the agent recover. We argue that the execution environment should instead enforce safety as the agent runs and steer it toward safe alternatives when violations occur---we call this Environment Steering. We implement this by modeling the agent and harness execution state as database tables, track the record-level data flows, and check these data flows against declarative policies during runtime. When violations are detected, policy- and context-specific feedback steers the agent toward safe trajectories. On AgentDyn, this enables the agent to improve task success rate over no-defense while achieving 0% attack success rate.

Computation and Language (cs.CL); Artificial Intelligence (cs.AI); Databases (cs.DB)

arXiv:2609.35807 [cs.CL]

(or arXiv:2609.35807v1 [cs.CL] for this version)

https://doi.org/10.48550/arXiv.2609.35807 Focus to learn more arXiv-issued DOI via DataCite (pending registration)

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

Full text under the publisher's open licence · 232 words

Related coverage