aiqbench analysis
This arXiv paper proposes a control plane that keeps enterprise AI agents from executing altered actions, reusing permissions, or double-applying retried operations, by enforcing authorization in trusted gateways rather than in the agent's reasoning. The reported results (one successful claim per allowance across 6,560 concurrent attempts) come from a single-host etcd setup with synthetic inputs and a mock target, so they show the mechanism works under controlled conditions, not that it is production-ready. Readers building agent systems should note the authors' own caveats: distributed reservations, real-target exactly-once effects, and interoperability remain untested, and a permissive policy still allowed an undesirable action.
KedgeFlow: A Programmable Control Plane for Enterprise AI Agents
arXiv:2610.14810v1 Announce Type: cross Abstract: Enterprise AI agents can execute altered versions of approved actions, concurrently reuse the same permission, or retry operations whose responses were lost. These failures arise when approval and resource execution lack a shared contract. KedgeFlow specifies language-independent contracts for trusted controllers to authorize state-changing operations and privileged gateways to enforce that authority independently of agent reasoning. Inspired by OpenFlow, it connects policy checks supported by evidence, signed permission for an exact action, a shared allowance that can be consumed only once, target-side conditions for applying the change, and retained outcome records. Under trusted issuance of exact-action authority, two conditional properties establish at most one successful claim per allowance and link every governed dispatch to a matching grant, claim, and subsequent dispatch authorization, even when the agent is compromised. A reference implementation exposes this execution path to agent systems through the Model Context Protocol (MCP). In the single-resource evaluation, 6,560 concurrent ledger claim attempts yielded exactly one successful claim for each of 82 allowances. Boundary tests rejected unauthorized and altered requests before consumption. A 32-call gateway race produced one committed mock effect, and a retry after a lost response produced no additional dispatch. Deliberately permissive policy nevertheless authorized an undesirable effect, exposing the limits of execution authorization. Evaluation uses three members of the etcd coordinated key-value store on one host, synthetic authentication and authorization inputs, and a mock target that rejects stale requests. Distributed reservations, enforcement of every production access route, native crash recovery, exactly-once effects at real targets, and interoperability between independent implementations remain untested.
Abstract:Enterprise AI agents can execute altered versions of approved actions, concurrently reuse the same permission, or retry operations whose responses were lost. These failures arise when approval and resource execution lack a shared contract. KedgeFlow specifies language-independent contracts for trusted controllers to authorize state-changing operations and privileged gateways to enforce that authority independently of agent reasoning. Inspired by OpenFlow, it connects policy checks supported by evidence, signed permission for an exact action, a shared allowance that can be consumed only once, target-side conditions for applying the change, and retained outcome records. Under trusted issuance of exact-action authority, two conditional properties establish at most one successful claim per allowance and link every governed dispatch to a matching grant, claim, and subsequent dispatch authorization, even when the agent is compromised. A reference implementation exposes this execution path to agent systems through the Model Context Protocol (MCP). In the single-resource evaluation, 6,560 concurrent ledger claim attempts yielded exactly one successful claim for each of 82 allowances. Boundary tests rejected unauthorized and altered requests before consumption. A 32-call gateway race produced one committed mock effect, and a retry after a lost response produced no additional dispatch. Deliberately permissive policy nevertheless authorized an undesirable effect, exposing the limits of execution authorization. Evaluation uses three members of the etcd coordinated key-value store on one host, synthetic authentication and authorization inputs, and a mock target that rejects stale requests. Distributed reservations, enforcement of every production access route, native crash recovery, exactly-once effects at real targets, and interoperability between independent implementations remain untested.
12 pages, 1 figure, 3 tables. Code and artifact available at this https URL
Distributed, Parallel, and Cluster Computing (cs.DC); Cryptography and Security (cs.CR); Machine Learning (cs.LG)
C.2.4; D.4.6; I.2.11; D.2.11
arXiv:2610.14810 [cs.DC]
(or arXiv:2610.14810v1 [cs.DC] for this version)
https://doi.org/10.48550/arXiv.2610.14810 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 · 377 words
Related coverage

News
Quantum Computing Report · Jun 7, 2026

NVIDIA BlueField-4 Powers New Scale-In Network Infrastructure for Agentic AI Factories
NVIDIA · Aug 24, 2026
Equinix turns the network into the control plane for enterprise AI inference
ZK Research · Sep 5, 2026

Intel Puts Agentic AI to Work with Xeon 6+, Networking, and AI Systems
Intel · Jun 1, 2026