Lists EKS clusters in the current region.
AI agents call list_eks_clusters 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 EKS cluster metadata and returns information without creating, modifying, deleting, or executing any actions. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—an attacker gains visibility into cluster names and metadata but cannot alter infrastructure. Low severity is appropriate for an informational read operation on infrastructure metadata.
From the tool's definition Tool name is 'list_eks_clusters' and description states it 'Lists EKS clusters in the current region.' The verb 'Lists' indicates a read operation that retrieves data without modification.
Attacks that exploit this kind of access
Lists EKS clusters in the current 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_eks_clusters: 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_eks_clusters 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_eks_clusters 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_eks_clusters. 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_eks_clusters 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 →