为编码智能体设计可撤销权限机制,防止资源滥用
Lingering Authority: Revocable Resource-and-Effect Capabilities for Coding Agents
- 引入PORTICO监控器,通过合约管理权限生命周期
- 实验显示可撤销系统成功阻止10/10次违规后续使用
- 适合需要严格资源控制的自动化开发场景
编码智能体常在整项任务中拥有广泛工具访问权,即使某资源仅用于单一子目标。这种权限持续存在的现象称为‘残留权限’。PORTICO是一种参考监控器,用于管理规划器暴露的可撤销能力。它将显式任务合约编译为初始权限、授予权则、可信关闭谓词和全局拒绝规则。请求-授权-调用生命周期将权限扩展为不可见的、时限绑定的句柄。关闭时,这些句柄从下一轮规划接口移除,并拒绝过期重放前的副作用。监控器假设工具经过中介且目录类型正确。在受控编码任务中,PORTICO在评估运行中未记录任何合同禁止的执行效果;而受限授予恢复了被固定窄范围封锁的边界工作。非可撤销对比系统接收相同初始范围与相同轮次授予。在关闭阶段,两者任务成功率、作用域合规性及所有关闭前决策一致;但PORTICO拒绝10/10次后续重用,对比系统允许10/10次。确定性旧写审计记录0/6对比6/6次违规执行。脚本追踪与六次真实模型追踪(文件写入、git变更、网络外发)均显示相同差异。四轮同策略诊断中,广泛请求暴露虽保持零违规执行,但被阻提案数由67升至84。真实仓库冻结运行记录提交与追踪,在真实项目结构上验证了同一生命周期。
原文摘要 · Abstract (English)
Coding agents often receive broad tool access for an entire task, even when a resource is needed only for one subgoal. We call this gap lingering authority: a temporary resource/effect capability remains exposed after the episode that justified it has closed. PORTICO is a reference monitor for revocable capabilities exposed to the planner. It compiles an explicit task contract into initial capabilities, grant rules, trusted closure predicates, and global deny rules. A request-grant-invoke lifecycle materializes expansions as opaque, epoch-bound handles. Closure removes those handles from the next planner interface and rejects stale replay before side effects. The monitor assumes mediated tools and a sound typed catalog. In controlled coding-agent tasks, PORTICO records no executed contract-forbidden effects in the evaluated runs, while controlled grants recover boundary work blocked by a fixed narrow envelope. A non-revoking comparator receives the same initial envelope and the same grants at the same turns. On the closure slice, both systems match task success, scope compliance, and all pre-closure decisions; PORTICO then rejects 10/10 post-closure reuses, while the comparator permits 10/10. A deterministic stale-write audit records 0/6 versus 6/6 executed forbidden effects. Scripted traces and six live model traces over file writes, git mutation, and network egress show the same split. In a four-episode same-policy diagnostic, broad request exposure preserves zero executed forbidden effects but raises blocked proposals from 67 to 84. Frozen real-repository runs, with commits and traces recorded, exercise the same lifecycle on real project layouts.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。