Auto-Policy, not Auto-Skill: Compiled Agent Skills for the Physical World
Organizations: Imperial College London London, UK
Abstract
Self-evolving Skill harnesses (AutoSkills, Hermes Agent) generate more advisory orchestration automatically; their reported gains are efficiency, not safety. This misses the actual gap: a Skill describes how an agent should behave; a Policy decides which behavior is allowed to become an action. Today's format covers the first with markdown and scripts; the second is left to the model. Generating more Skills scales the gap, not the safety, especially when a wrong invocation can unlock a door or move money. Two adjacent attacks are documented: malicious skills compromising cloud software, and jailbroken LLM-controlled robots causing physical harm. Their intersection, malicious agent skills causing physical harm, follows directly but has not been reported. We name this class Borrowed Authority: Skills format gives the receiving agent no typed way to reject an inter-agent permission claim, so a malicious or misused Skill can drive actuation by attaching one. We propose Edge Skillguard, a typed authority layer that lives inside the Skill artifact rather than between tools as workflow engines do, with guards over world state and sensor evidence. On a live edge control-plane testbed, the guards reject 60/60 borrowed-authority requests across five attack variants without blocking benign requests, and the result holds at 5x scale and across hosts over a Tailscale mesh. These results suggest that high-risk Skills should co-package typed invocation policy with procedural knowledge, so that physical actions depend on machine-checkable evidence rather than peer-agent claims.
Figures & tables
Today'': a Manager agent sends a natural-language message reading unlock front door; presence confirmed'' to a Lock agent, which actuates a door unlock. Bottom row labeled ``With Edge Skillguard'': the same Manager agent sends the same message to an Edge Skillguard typed guard, which blocks the request because the substrate carries no fresh presence_token evidence backing the claim.| Cloud / software harm | Physical-state harm | |
|---|---|---|
| Compromised LLM runtime | Documented ( Greshake et al., 2023 ) | Documented ( Robey et al., 2025 ) |
| Compromised skill artifact | Documented ( Liu et al., 2026 ; Check Point Research, 2026 ) | Open—this paper |
| Metric | Skill | NL M2M | ESG-LO | ESG |
| Wrongful actuation (attack) | 60/60 | 60/60 | 24/60 | 0/60 |
| Benign success | 60/60 | 60/60 | 60/60 | 60/60 |
| LLM calls per decision | 1 | 1 | 0 | 0 |
| Median latency, in-process | LLM | LLM | 1.5 s | 3.2 s |
| Median latency, local broker | — | — | — | 273 s |
| Median latency, Tailscale mesh | — | — | — | 5.7 ms |
Runtime Enforcement for AI Agents
Runtime enforcement for AI agents checks and constrains actions as they execute, helping prevent unsafe or unauthorized effects.
See all 276 papers