Modifies VM CPU/RAM/GUI settings. Triggers a reboot if the VM is running.
AI agents use resize_vm_resources to create or update resources in Virtualbox MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Virtualbox MCP Server environment.
This tool modifies VM resource configuration (CPU, RAM, GUI settings), which is a reversible write operation. However, it also triggers a reboot of running VMs as a side effect, which can cause service interruption. The blast radius is high because misuse could disrupt running workloads by causing unexpected reboots or misconfiguring critical VM resources.
From the tool's definition Modifies VM CPU/RAM/GUI settings. Triggers a reboot if the VM is running.
Attacks that exploit this kind of access
Modifies VM CPU/RAM/GUI settings. Triggers a reboot if the VM is running. It is categorised as a Write tool in the Virtualbox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Virtualbox MCP Server MCP server in PolicyLayer and add a rule for resize_vm_resources: 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.
resize_vm_resources is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resize_vm_resources 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 resize_vm_resources. 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.
resize_vm_resources 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 →