ExecuteRangeQuery
AI agents invoke ExecuteRangeQuery to trigger actions in Amazon MQ 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.
The 'Execute' prefix strongly suggests this tool runs queries or operations with side effects that depend on runtime arguments. Without a description, confidence is reduced but the verb 'Execute' in the name is a reliable indicator.
From the tool's definition Tool name 'ExecuteRangeQuery' indicates query execution; description is empty, so classification relies on the verb 'Execute' which implies running code or operations whose effects depend on arguments.
Attacks that exploit this kind of access
ExecuteRangeQuery. It is categorised as a Execute tool in the Amazon MQ MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon MQ 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 MQ 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 MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.