Lists subnets with availability zones and available IP counts.
AI agents call list_subnets to retrieve information from AWS 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 AWS infrastructure metadata (subnets, zones, IP availability) without modifying, deleting, or executing any operations. It is a pure read operation consistent with the server's documented read-only access model. The information returned is informational only and poses minimal risk if accessed by an AI agent.
From the tool's definition Tool name is 'list_subnets' and description states it 'Lists subnets with availability zones and available IP counts.' The verb 'lists' and the read-only nature of the server (stated as 'read-only' in server description) confirm this is a retrieval operation…
Attacks that exploit this kind of access
Lists subnets with availability zones and available IP counts. It is categorised as a Read tool in the AWS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for list_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 AWS MCP Server. Nothing to install.
list_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_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_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_subnets is provided by the AWS MCP Server MCP server (sergiosediq/aws-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 →