Remove network interface from virtual machine
AI agents call remove_nic_from_vm to permanently remove resources in CloudStack MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a NIC from a VM is a destructive operation: it severs network connectivity for that interface, and the removal itself cannot be trivially undone (re-adding a NIC may not restore the same configuration, IP assignments, etc.). Given the blast radius — potential loss of network access to a running VM — severity is high.
From the tool's definition 'Remove network interface from virtual machine' — removing a NIC is an irreversible network configuration change that disconnects the VM from a network segment
Attacks that exploit this kind of access
Remove network interface from virtual machine. It is categorised as a Destructive tool in the CloudStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for remove_nic_from_vm: 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 CloudStack MCP Server. Nothing to install.
remove_nic_from_vm 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 remove_nic_from_vm 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 remove_nic_from_vm. 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.
remove_nic_from_vm is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →