AI agents invoke ExecuteRangeQuery to trigger actions in Amazon EKS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
ExecuteRangeQuery performs an active operation (query execution) that could read from or interact with EKS cluster state. Without a description, the tool cannot be confirmed as purely Read (which would suggest passive retrieval). The 'Execute' verb and lack of additional context suggests this runs queries with non-deterministic results based on cluster state.
From the tool's definition Tool name 'ExecuteRangeQuery' indicates execution of a query operation. No description provided, but 'Execute' in the name suggests running a query against EKS data or resources.
Documented attack patterns abuse exactly the kind of access ExecuteRangeQuery gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ExecuteRangeQuery:
{
"version": "1",
"default": "deny",
"tools": {
"ExecuteRangeQuery": {
"limits": [
{
"counter": "executerangequery_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ExecuteRangeQuery stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
ExecuteRangeQuery. It is categorised as a Execute tool in the Amazon EKS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for ExecuteRangeQuery: 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 Amazon EKS MCP Server. Nothing to install.
ExecuteRangeQuery is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ExecuteRangeQuery 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 ExecuteRangeQuery. 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.
ExecuteRangeQuery is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon EKS 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.
805 Amazon EKS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.