Create a new Vagrant VM
AI agents invoke create_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.
Creating a VM involves executing external processes (Vagrant/VirtualBox commands) that provision real infrastructure. While it is not purely destructive or financial, it executes significant external operations with resource implications (CPU, memory, disk, networking). Misuse could spin up many VMs, exhausting host resources or incurring cloud costs if backed by a cloud provider.
From the tool's definition 'Create a new Vagrant VM' — provisions and launches a new virtual machine via Vagrant, triggering external infrastructure operations
Attacks that exploit this kind of access
Create a new Vagrant VM. 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 create_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.
create_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 create_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 create_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.
create_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 →