Upload a file from host to VM
AI agents use upload_file 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.
Uploading files to a VM creates or modifies files in the VM's filesystem. While reversible (files can be deleted), this is a Write operation rather than Read (it changes state). The severity is high because uploaded files could include malicious scripts, configurations, or data that compromise the VM or introduce security vulnerabilities.
From the tool's definition Tool performs 'upload_file' from host to VM, which modifies the VM's filesystem by adding or changing files. This is a reversible write operation that changes data on the target system.
Attacks that exploit this kind of access
Upload a file from host to VM. 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 upload_file: 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.
upload_file 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 upload_file 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 upload_file. 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.
upload_file 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 →