proxmox_vm_nic_remove
A destructive tool on the MCP Proxmox MCP server.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-vm-nic-remove.md
What proxmox_vm_nic_remove does on MCP Proxmox Server
AI agents call proxmox_vm_nic_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_vm_nic_remove is rated Critical
The tool performs an irreversible destructive action on VM infrastructure. Removing a network interface from a running or configured VM breaks connectivity and cannot be automatically reversed without explicit reconfiguration. In a Proxmox cluster management context with full API access, this poses critical risk if an AI agent is misdirected to remove network interfaces from production VMs.
From the tool's definition Tool name 'proxmox_vm_nic_remove' indicates removal of network interface card from a virtual machine. This is an irreversible network configuration change that cannot be easily undone and matches the Destructive category pattern of removing/detaching…
Attacks that exploit this kind of access
The rule that runs proxmox_vm_nic_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_vm_nic_remove, this is the rule to start with:
proxmox_vm_nic_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_vm_nic_remove call is checked against it from then on.
Questions about proxmox_vm_nic_remove
proxmox_vm_nic_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_vm_nic_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_vm_nic_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_vm_nic_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_vm_nic_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_vm_nic_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