upload_to_storage
A write tool on the Proxmox MCP server.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/upload-to-storage.md
What upload_to_storage does on Proxmox MCP Server
AI agents use upload_to_storage to create or update resources in Proxmox MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxmox MCP Server environment.
Why upload_to_storage is rated Medium
Uploading to storage creates or modifies data in a Proxmox VE environment. While reversible (data can be deleted), the blast radius is high because malicious uploads could introduce malware, corrupt VM/container images, exhaust storage capacity, or poison infrastructure templates. This is Write rather than Destructive because uploads are generally reversible.
From the tool's definition Tool name 'upload_to_storage' indicates file/data write operation to Proxmox storage backend. Description is empty, limiting direct evidence, but naming convention and context within infrastructure management tools strongly suggests data creation/modification.
Attacks that exploit this kind of access
The rule that runs upload_to_storage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_to_storage, this is the rule to start with:
upload_to_storage stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every upload_to_storage call is checked against it from then on.
Questions about upload_to_storage
upload_to_storage is a write tool on the Proxmox MCP Server MCP server. It is categorised as a Write tool in the Proxmox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for upload_to_storage: 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 Proxmox MCP Server. Nothing to install.
upload_to_storage 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_to_storage 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_to_storage. 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_to_storage is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
This server
Across the catalogue