Get VPC configuration for an EKS cluster. This tool retrieves comprehensive VPC configuration details for any EKS cluster, including CIDR blocks and route tables which are essential for understanding network connectivity. For hybrid node setups, it also automatically identifies and includes remo...
Part of the Amazon EKS MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_eks_vpc_config to retrieve information from Amazon EKS MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_eks_vpc_config only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_eks_vpc_config:
rules:
- action: allowSee the full Amazon EKS MCP Server policy for all 16 tools.
Agents calling read-class tools like get_eks_vpc_config have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get VPC configuration for an EKS cluster. This tool retrieves comprehensive VPC configuration details for any EKS cluster, including CIDR blocks and route tables which are essential for understanding network connectivity. For hybrid node setups, it also automatically identifies and includes remote node and pod CIDR configurations. ## Requirements - The server must be run with the `--allow-sensitive-data-access` flag ## Response Information The response includes VPC CIDR blocks, route tables, and when available, remote CIDR configurations for hybrid node connectivity. ## Usage Tips - Understand VPC networking configuration for any EKS cluster - Examine route tables to verify proper network connectivity - For hybrid setups: Check that remote node CIDR blocks are correctly configured - For hybrid setups: Verify that VPC route tables include routes for hybrid node CIDRs Args: ctx: MCP context cluster_name: Name of the EKS cluster vpc_id: Optional ID of the specific VPC to query Returns: EksVpcConfigResponse with VPC configuration details. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_eks_vpc_config. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon EKS MCP Server MCP server.
get_eks_vpc_config 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 get_eks_vpc_config rule in your Intercept 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 Intercept policy for get_eks_vpc_config. 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.
get_eks_vpc_config is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.