List all VPC subnets
AI agents call list_vpc_subnets 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 and queries VPC subnet information without modifying, deleting, or executing any operations. It has no side effects beyond returning data. Read-only operations on infrastructure metadata pose minimal risk unless the queried data itself is sensitive, but even then misuse would only expose information rather than cause damage.
From the tool's definition Tool name 'list_vpc_subnets' and description 'List all VPC subnets' indicate a retrieval operation. Server is explicitly marked 'Read-only MCP server' and all sibling tools are read-only operations (get_*, list_*, clear_credentials).
Attacks that exploit this kind of access
List all VPC subnets. 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_vpc_subnets: 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_vpc_subnets 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_vpc_subnets 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_vpc_subnets. 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_vpc_subnets 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 →