Execute a PromQL range query
AI agents invoke prom_range to trigger actions in Prometheus 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.
Executing a PromQL range query is an active operation that runs user-supplied query expressions against the Prometheus backend. While Prometheus queries are read-only by nature (no data modification), 'Execute' is more appropriate than 'Read' because the tool runs arbitrary query code whose computational cost and behavior depend on the arguments supplied (e.g., expensive queries can overload the server).
From the tool's definition "Execute a PromQL range query" — the tool runs an arbitrary PromQL expression against Prometheus over a time range.
Attacks that exploit this kind of access
Execute a PromQL range query. It is categorised as a Execute tool in the Prometheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for prom_range: 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 Prometheus MCP Server. Nothing to install.
prom_range 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 prom_range 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 prom_range. 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.
prom_range is provided by the Prometheus MCP Server MCP server (yanmxa/prometheus-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 →