proxmox_pool_remove
A destructive tool on the MCP Proxmox MCP server.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-pool-remove.md
What proxmox_pool_remove does on MCP Proxmox Server
AI agents call proxmox_pool_remove to permanently remove resources in MCP Proxmox Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why proxmox_pool_remove is rated Critical
Although the tool description is empty, the name 'proxmox_pool_remove' combined with the server's capability to manage virtualization infrastructure strongly suggests an irreversible deletion operation. Pool removal in Proxmox environments typically cannot be undone and affects resource management persistently. This makes it Destructive rather than Write.
From the tool's definition Tool name 'proxmox_pool_remove' indicates removal/deletion of a resource pool in Proxmox infrastructure. In the context of 'comprehensive management of Proxmox virtualization infrastructure' with 'VM/LXC lifecycle operations,' removing a pool would…
Attacks that exploit this kind of access
The rule that runs proxmox_pool_remove safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_pool_remove, this is the rule to start with:
proxmox_pool_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Proxmox Server, apply this rule, and every proxmox_pool_remove call is checked against it from then on.
Questions about proxmox_pool_remove
proxmox_pool_remove is a destructive tool on the MCP Proxmox Server MCP server. It is categorised as a Destructive tool in the MCP Proxmox Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_pool_remove: 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 MCP Proxmox Server. Nothing to install.
proxmox_pool_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the proxmox_pool_remove 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 proxmox_pool_remove. 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.
proxmox_pool_remove is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Proxmox Server, and thousands of servers like it.
Across the catalogue