execute_promql_range_query
AI agents invoke execute_promql_range_query to trigger actions in AWS Labs postgres 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.
PromQL query execution can interact with external systems (Prometheus, monitoring infrastructure) and potentially trigger alerts, data aggregation operations, or retrieve sensitive metrics. While primarily a query tool, the 'execute' naming and potential for complex operations that depend on query arguments place this in the Execute category.
From the tool's definition Tool name 'execute_promql_range_query' indicates execution of PromQL (Prometheus Query Language) range queries.
Attacks that exploit this kind of access
execute_promql_range_query. It is categorised as a Execute tool in the AWS Labs postgres MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Labs postgres MCP Server MCP server in PolicyLayer and add a rule for execute_promql_range_query: 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 Labs postgres MCP Server. Nothing to install.
execute_promql_range_query 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 execute_promql_range_query 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 execute_promql_range_query. 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.
execute_promql_range_query is provided by the AWS Labs postgres MCP Server MCP server (awslabs.postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.