cloud_sandbox_create
Create a new cloud sandbox (Linux VM). Returns sandbox ID and connection info.
This record as markdown: /tools/cowork-os/cloud-sandbox-create.md
What cloud_sandbox_create does on CoWork OS
AI agents invoke cloud_sandbox_create to trigger actions in CoWork OS. 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.
Why cloud_sandbox_create is rated High
This tool provisions a new cloud Linux virtual machine, which is an external infrastructure operation. Spinning up VMs has real-world side effects (resource consumption, potential costs, network exposure) and enables arbitrary code execution within the sandbox.
From the tool's definition Create a new cloud sandbox (Linux VM)
Attacks that exploit this kind of access
The rule that runs cloud_sandbox_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cloud_sandbox_create, this is the rule to start with:
cloud_sandbox_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every cloud_sandbox_create call is checked against it from then on.
Questions about cloud_sandbox_create
Create a new cloud sandbox (Linux VM). Returns sandbox ID and connection info. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CoWork OS MCP server in PolicyLayer and add a rule for cloud_sandbox_create: 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 CoWork OS. Nothing to install.
cloud_sandbox_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cloud_sandbox_create 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 cloud_sandbox_create. 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.
cloud_sandbox_create is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue