remoteos_create_instance

Create a new Incus system container or micro-VM on the BDB SaaS Host fleet with zero-trust guardrails.

SERVERAos SOURCE@hybridlabor-api/aos

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/remoteos-create-instance.md

WHAT IT DOES

What remoteos_create_instance does on Aos

AI agents invoke remoteos_create_instance to trigger actions in Aos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why remoteos_create_instance is rated High

Spawns new compute instances on remote infrastructure, triggering significant external operations.

From the tool's definition Create a new Incus system container or micro-VM

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remoteos_create_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_create_instance, this is the rule to start with:

remoteos_create_instance Rate-limited

remoteos_create_instance stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remoteos_create_instance": {
      "limits": [
        {
          "counter": "remoteos_create_instance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every remoteos_create_instance call is checked against it from then on.

FAQ

Questions about remoteos_create_instance

What does the remoteos_create_instance tool do? +

Create a new Incus system container or micro-VM on the BDB SaaS Host fleet with zero-trust guardrails. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on remoteos_create_instance? +

Register the Aos MCP server in PolicyLayer and add a rule for remoteos_create_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.

What risk level is remoteos_create_instance? +

remoteos_create_instance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit remoteos_create_instance? +

Yes. Add a rate_limit block to the remoteos_create_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.

How do I block remoteos_create_instance completely? +

Set action: deny in the PolicyLayer policy for remoteos_create_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.

What MCP server provides remoteos_create_instance? +

remoteos_create_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.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools → High-risk tools on this server →

Across the catalogue

diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →