New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_nic_from_vm

Remove network interface from virtual machine

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/remove-nic-from-vm.md

What remove_nic_from_vm does on CloudStack MCP Server

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.

Why remove_nic_from_vm is rated Critical

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

Questions about remove_nic_from_vm

What does the remove_nic_from_vm tool do? +

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.

How do I enforce a policy on remove_nic_from_vm? +

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.

What risk level is remove_nic_from_vm? +

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.

Can I rate-limit remove_nic_from_vm? +

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.

How do I block remove_nic_from_vm completely? +

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.

What MCP server provides remove_nic_from_vm? +

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.

More on CloudStack MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CloudStack MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.