get_virtual_machine

THE RISK

Low Risk

Why get_virtual_machine needs a policy

This tool retrieves and queries metadata about a virtual machine. It has no side effects, does not modify infrastructure, and does not execute commands or operations. It is a straightforward read operation typical of infrastructure query/inspection tools.

From the tool's definition Tool name is 'get_virtual_machine' and description states 'Get details of a specific virtual machine' — indicates retrieval of existing data with no modification, deletion, or execution of operations.

Documented attack patterns abuse exactly the kind of access get_virtual_machine gives an agent:

POLICY

How to control get_virtual_machine

PolicyLayer is an MCP gateway — it sits between your AI agents and CloudStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_virtual_machine:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_virtual_machine": {}
  }
}

get_virtual_machine is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register CloudStack MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CloudStack MCP Server tools

Destructive destroy_virtual_machine Destroy a virtual machine using proper workflow: stop → destroy → expunge. Handles VMs in Execute deploy_virtual_machine Deploy a new virtual machine Execute scale_virtual_machine Scale virtual machine (change service offering) Execute start_virtual_machine Start a virtual machine Execute stop_virtual_machine Stop a virtual machine Execute reboot_virtual_machine Reboot a virtual machine Execute migrate_virtual_machine Migrate virtual machine to another host Write reset_password_virtual_machine Reset password for virtual machine

All 45 CloudStack MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_virtual_machine

What does the get_virtual_machine tool do? +

Get details of a specific virtual machine. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_virtual_machine? +

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

get_virtual_machine is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_virtual_machine? +

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

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

get_virtual_machine is provided by the CloudStack MCP Server MCP server (phantosmax/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CloudStack MCP Server tool call.

Start from CloudStack MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →