This record as markdown: /tools/hybridlabor-api-aos/remoteos-manage-instance.md
What remoteos_manage_instance does on Aos
AI agents call remoteos_manage_instance to permanently remove resources in Aos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remoteos_manage_instance is rated Critical
Deleting or stopping an instance is irreversible and high-blast-radius.
From the tool's definition start, stop, restart, delete of an Incus instance
Attacks that exploit this kind of access
The rule that runs remoteos_manage_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remoteos_manage_instance, this is the rule to start with:
remoteos_manage_instance is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every remoteos_manage_instance call is checked against it from then on.
Questions about remoteos_manage_instance
Manage lifecycle (start, stop, restart, delete) of an Incus instance. Destructive actions trigger 4-eyes approval queue. It is categorised as a Destructive tool in the Aos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aos MCP server in PolicyLayer and add a rule for remoteos_manage_instance: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Aos. Nothing to install.
remoteos_manage_instance is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remoteos_manage_instance rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for remoteos_manage_instance. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
remoteos_manage_instance is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
Across the catalogue