List all virtual machines
AI agents call list_virtual_machines to retrieve information from Yandex Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about virtual machines with no side effects. It falls squarely into the Read category. The server's explicit read-only designation and the sibling tools (all prefixed with 'get_', 'list_', or 'clear_credentials') reinforce this classification. Severity is low because listing VMs exposes information but does not modify infrastructure or enable direct resource manipulation.
From the tool's definition Tool name is 'list_virtual_machines' and server is explicitly described as 'Read-only MCP server'. The tool performs a list operation which retrieves data without modification.
Attacks that exploit this kind of access
List all virtual machines. It is categorised as a Read tool in the Yandex Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yandex Cloud 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 Yandex Cloud 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 Yandex Cloud MCP Server MCP server (romati88/ycmcp). 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 →