add_nic_to_vm · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_nic_to_vm does on CloudStack MCP Server

AI agents use add_nic_to_vm 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_vm needs a policy

Adding a network interface modifies VM state and network connectivity but is not destructive (the NIC can be removed). This is a Write operation that could have significant blast radius if misused (e.g., connecting a VM to an unintended network, enabling unauthorized access paths), hence high severity. The confidence is high given the explicit action verb 'add' and clear infrastructure modification scope.

From the tool's definition Tool name 'add_nic_to_vm' and description 'Add network interface to virtual machine' indicates creation/modification of VM network configuration. This is a reversible write operation—NICs can be removed or reconfigured.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_nic_to_vm Rate-limited

add_nic_to_vm 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_vm": {
      "limits": [
        {
          "counter": "add_nic_to_vm_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_vm

What does the add_nic_to_vm tool do? +

Add network interface to 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_vm? +

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

add_nic_to_vm 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_vm? +

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

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

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