resize_container_disk
Resize a container disk/volume.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/resize-container-disk.md
What resize_container_disk does on Proxmox MCP Server
AI agents use resize_container_disk 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 resize_container_disk is rated Medium
The tool modifies container storage configuration, placing it in the Write category rather than Destructive. Severity is high because misconfiguration (e.g., shrinking below required capacity) could cause container malfunction or data loss, though the operation itself is technically reversible. Confidence is high given the clear name and description indicating a modification operation on Proxmox infrastructure.
From the tool's definition resize_container_disk resizes a container disk/volume—modifying storage configuration. This is a reversible write operation: the disk size can be changed again later, distinguishing it from destructive deletion.
Attacks that exploit this kind of access
The rule that runs resize_container_disk 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 resize_container_disk, this is the rule to start with:
resize_container_disk 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 resize_container_disk call is checked against it from then on.
Questions about resize_container_disk
Resize a container disk/volume. 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 resize_container_disk: 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.
resize_container_disk 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_container_disk 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_container_disk. 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_container_disk 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