Permission to Work, Not to Escape: Policies, Controls and Escalating Enforcement Across AI Agents
Allister Lundberg
All agents working on a project must stay within a project's scope, even if their technical access is broader. I designed and tested an approach that compiles project policies into executable controls, preserves restrictions across delegated workers, and escalates verified violations from warnings to project wide stops. Using 200 tests adapted from five security benchmarks, I tested whether these controls blocked unauthorized actions while preserving authorized work. Enforcement correctly blocked all 133 unauthorized tool actions, which were not blocked under baseline protection and sandbox protection alone, while allowing all 200 scripted authorized actions. Compiling typed LLM proposals was found to avoid errors seen in direct policy generation. A further test counted violations across the parent and its workers, where the first violation triggered a warning and the next successfully stopped the parent and both delegated workers. These results support a mechanism for protection from swarm attacks by applying project controls across agents and delegates and escalating enforcement in response to their combined violations with minimal overhead in LLM usage with runtime checks requiring no additional LLM calls.
No reviews are available yet
Cite this work
@misc {
title={
(HckPrj) Permission to Work, Not to Escape: Policies, Controls and Escalating Enforcement Across AI Agents
},
author={
Allister Lundberg
},
date={
},
organization={Apart Research},
note={Research submission to the research sprint hosted by Apart.},
howpublished={https://apartresearch.com}
}


