List virtual machines in CloudStack with comprehensive filtering options
AI agents call list_virtual_machines to retrieve information from CloudStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data about virtual machines without modifying, deleting, or executing any infrastructure changes. It is a read-only operation that provides information to the user. The comprehensive filtering options mentioned are query parameters, not actions that alter state.
From the tool's definition Tool name is 'list_virtual_machines' and description states it 'List virtual machines in CloudStack with comprehensive filtering options' - the verb 'list' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
List virtual machines in CloudStack with comprehensive filtering options. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for list_virtual_machines: 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.
list_virtual_machines 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_virtual_machines 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_virtual_machines. 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_virtual_machines 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.
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 →