add_nic_to_virtual_machine

What add_nic_to_virtual_machine does on CloudStack MCP Server

AI agents use add_nic_to_virtual_machine to create or update resources in CloudStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

Why add_nic_to_virtual_machine is rated Medium

This tool creates/modifies VM configuration by adding a network interface card. While it modifies infrastructure state and could impact network connectivity if misconfigured, it is reversible (NICs can be detached) and does not destroy data or commit financial obligations. It falls under Write rather than Execute because it modifies a specific resource configuration rather than executing arbitrary code/commands.

From the tool's definition Tool name 'add_nic_to_virtual_machine' and description 'Add a NIC to a virtual machine' indicate a modification operation that creates a new network interface on a VM. This is a reversible change—NICs can be removed or replaced.

The rule that runs add_nic_to_virtual_machine safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_nic_to_virtual_machine, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_nic_to_virtual_machine": {
      "limits": [
        {
          "counter": "add_nic_to_virtual_machine_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about add_nic_to_virtual_machine