AI agents call list-vpcs 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 performs a read-only operation that queries and returns VPC metadata. It has no side effects, does not modify infrastructure, and poses minimal risk even if invoked by an AI agent. The blast radius is limited to information disclosure of existing VPC configurations.
From the tool's definition Tool name 'list-vpcs' and description 'List all the VPCs in the given region' indicate a query operation that retrieves information without modifying resources.
Documented attack patterns abuse exactly the kind of access list-vpcs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-vpcs:
{
"version": "1",
"default": "deny",
"tools": {
"list-vpcs": {}
}
}list-vpcs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all the VPCs in the given region. 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-vpcs: 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-vpcs 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-vpcs 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-vpcs. 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-vpcs is provided by the AWS MCP Server MCP server (lokeswaran-aj/aws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
54 AWS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.