import_unmanaged_instance · CloudStack MCP Server MCP

WHAT IT DOES

What import_unmanaged_instance does on CloudStack MCP Server

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

This tool performs a reversible data modification operation that integrates an external VM into CloudStack's management system. While it writes/creates a new management record, the action itself is not destructive (the VM isn't deleted) and doesn't execute arbitrary code or move funds.

From the tool's definition 'Import unmanaged instance' creates a new managed entity in CloudStack infrastructure by bringing an external/unmanaged VM under CloudStack management. The action modifies the infrastructure state by adding a resource to the managed inventory.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_unmanaged_instance Rate-limited

import_unmanaged_instance 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": {
    "import_unmanaged_instance": {
      "limits": [
        {
          "counter": "import_unmanaged_instance_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 import_unmanaged_instance

What does the import_unmanaged_instance tool do? +

Import unmanaged virtual machine instance. 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 import_unmanaged_instance? +

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

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

Can I rate-limit import_unmanaged_instance? +

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

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

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