Get detailed VM configuration
AI agents call get_virtual_machine_config 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 retrieves VM configuration data without modifying, deleting, or executing operations. It is purely informational. The read-only nature of the server and the 'get_' prefix confirm the Read category. Severity is low because configuration disclosure, while potentially sensitive, does not enable direct harm without further actions through other tools.
From the tool's definition Server is explicitly described as 'Read-only MCP server' and tool name/description indicate it 'Get[s] detailed VM configuration' with no modification capability.
Attacks that exploit this kind of access
Get detailed VM configuration. 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 get_virtual_machine_config: 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.
get_virtual_machine_config 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 get_virtual_machine_config 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 get_virtual_machine_config. 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.
get_virtual_machine_config 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 →