list_vms
AI agents call list_vms to retrieve information from Cloud VM MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations retrieve and present data without modifying state. While the description is empty (reducing confidence slightly), the tool name and server context clearly indicate this enumerates VMs. The blast radius is low—listing VMs reveals infrastructure but does not create, modify, delete, or execute actions.
From the tool's definition Tool name 'list_vms' indicates retrieval/enumeration of VMs. No description provided, but the server's stated capability includes 'list...VMs' and the sibling tools show this server performs both read operations (list_providers, get_vm_details) and control…
Attacks that exploit this kind of access
list_vms. It is categorised as a Read tool in the Cloud VM MCP MCP Server, which means it retrieves data without modifying state.
Register the Cloud VM MCP server in PolicyLayer and add a rule for list_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 Cloud VM MCP. Nothing to install.
list_vms is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_vms is provided by the Cloud VM MCP server (sondt2709/cloud-vm-mcp-py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →