Disassociate a route table from a subnet or internet gateway or virtual private gateway
AI agents use disassociate-route-table 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 modifies AWS infrastructure state by disassociating route tables from network resources. While it does not permanently delete the route table itself, it reversibly changes network routing configuration which could disrupt traffic flow. This is a Write operation (reversible modification) rather than Destructive because the route table and its associations can be re-established.
From the tool's definition Tool name is 'disassociate-route-table' and description states it 'Disassociate a route table from a subnet or internet gateway or virtual private gateway'. This modifies network routing configuration by removing associations.
Documented attack patterns abuse exactly the kind of access disassociate-route-table 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 disassociate-route-table:
{
"version": "1",
"default": "deny",
"tools": {
"disassociate-route-table": {
"limits": [
{
"counter": "disassociate-route-table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disassociate-route-table 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.
Disassociate a route table from a subnet or internet gateway or virtual private gateway. 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 disassociate-route-table: 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.
disassociate-route-table 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 disassociate-route-table 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 disassociate-route-table. 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.
disassociate-route-table 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.