Execute a PromQL instant query
AI agents invoke prom_query 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.
Although Prometheus is a read-only metrics store, executing arbitrary PromQL expressions is an active operation that can be computationally expensive and trigger heavy server load. It falls under Execute rather than Read because it runs a query (which may be complex or resource-intensive) rather than simply fetching a known resource. No data is written or deleted, so severity is medium rather than high.
From the tool's definition "Execute a PromQL instant query" — the tool actively executes a query expression against Prometheus
Attacks that exploit this kind of access
Execute a PromQL instant 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_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 Prometheus MCP Server. Nothing to install.
prom_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 prom_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 prom_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.
prom_query 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 →