Low Risk

list_hyperv_vms

list_hyperv_vms

How to control list_hyperv_vms ↓

What list_hyperv_vms does on Virtualization

AI agents call list_hyperv_vms to retrieve information from Virtualization without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_hyperv_vms needs a policy

Listing virtual machines retrieves information about existing VMs without modifying, deleting, or executing operations on them. This is a classic Read operation. Severity is low because exposing VM inventory data poses minimal risk even if misused—it does not enable destructive or execution capabilities. Confidence is slightly reduced due to the empty description, but the tool name is unambiguous.

From the tool's definition Tool name 'list_hyperv_vms' indicates a listing/querying operation on Hyper-V virtual machines. The verb 'list' is characteristic of read-only data retrieval.

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

How to control list_hyperv_vms

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_hyperv_vms": {}
  }
}

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

  1. Create a free account and register Virtualization — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_hyperv_vms

What does the list_hyperv_vms tool do? +

list_hyperv_vms. It is categorised as a Read tool in the Virtualization MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_hyperv_vms? +

Register the Virtualization MCP server in PolicyLayer and add a rule for list_hyperv_vms: 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 Virtualization. Nothing to install.

What risk level is list_hyperv_vms? +

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

Can I rate-limit list_hyperv_vms? +

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

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

list_hyperv_vms is provided by the Virtualization MCP server (sandraschi/virtualization-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Virtualization tool call.

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

Free to start. No card required.

56 Virtualization tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.