Ensure development VM is running, create if it doesn
AI agents invoke ensure_dev_vm to trigger actions in Virtualbox MCP Server. 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.
This tool performs conditional execution: it checks whether a development VM is running and, if not, creates and starts one. This involves triggering external VM lifecycle operations (creation, boot) whose effects depend on current state. Since it can create new infrastructure, it spans Write and Execute; Execute is the most appropriate category given that it starts/runs a VM process.
From the tool's definition 'Ensure development VM is running, create if it doesn' — the tool both checks state and conditionally creates/starts a VM, triggering external operations (VM creation and/or execution)
Attacks that exploit this kind of access
Ensure development VM is running, create if it doesn. It is categorised as a Execute tool in the Virtualbox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Virtualbox MCP Server MCP server in PolicyLayer and add a rule for ensure_dev_vm: 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 Virtualbox MCP Server. Nothing to install.
ensure_dev_vm 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 ensure_dev_vm 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 ensure_dev_vm. 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.
ensure_dev_vm is provided by the Virtualbox MCP Server MCP server (usemanusai/virtualbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →