add_nic_to_virtual_machine · CloudStack MCP Server MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why add_nic_to_virtual_machine needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_nic_to_virtual_machine Rate-limited

add_nic_to_virtual_machine stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about add_nic_to_virtual_machine

What does the add_nic_to_virtual_machine tool do? +

Add a NIC to a virtual machine. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_nic_to_virtual_machine? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for add_nic_to_virtual_machine: 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 add_nic_to_virtual_machine? +

add_nic_to_virtual_machine is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_nic_to_virtual_machine? +

Yes. Add a rate_limit block to the add_nic_to_virtual_machine 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 add_nic_to_virtual_machine completely? +

Set action: deny in the PolicyLayer policy for add_nic_to_virtual_machine. 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 add_nic_to_virtual_machine? +

add_nic_to_virtual_machine 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.