AI agents use create-vpc to create or update resources in AWS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS MCP Server environment.
This tool creates new AWS VPC infrastructure resources, which is a reversible modification operation. While VPC creation has significant blast radius (can establish foundational network topology affecting multiple resources and potentially incurring AWS costs), it is not irreversible (VPCs can be deleted) and does not move money directly.
From the tool's definition Tool name is 'create-vpc' with description 'Create a new VPC in the given region'. The verb 'create' indicates data creation. VPC creation is a reversible infrastructure modification—VPCs can be deleted, making this Write rather than Destructive.
Documented attack patterns abuse exactly the kind of access create-vpc 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 create-vpc:
{
"version": "1",
"default": "deny",
"tools": {
"create-vpc": {
"limits": [
{
"counter": "create-vpc_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-vpc stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new VPC in the given region. It is categorised as a Write tool in the AWS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for create-vpc: 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.
create-vpc is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-vpc 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 create-vpc. 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.
create-vpc 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.