update_storage
A write tool on the Proxmox MCP server.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/update-storage.md
What update_storage does on Proxmox MCP Server
AI agents use update_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 update_storage is rated Medium
The tool name 'update_storage' most directly indicates modification of storage settings or metadata rather than creation (Write) or irreversible deletion (Destructive). Without a description, confidence is reduced but the Proxmox infrastructure context and naming convention suggest Write-class capabilities.
From the tool's definition Tool name 'update_storage' in Proxmox MCP Server context; empty description limits direct evidence but naming pattern indicates modification of storage configuration or state.
Attacks that exploit this kind of access
The rule that runs update_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 update_storage, this is the rule to start with:
update_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 update_storage call is checked against it from then on.
Questions about update_storage
update_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 update_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.
update_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 update_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 update_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.
update_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