query_prometheus

Query Prometheus using a PromQL expression. Supports both instant and range queries.

SERVERGrafana MCP Server SOURCE0xteamhq/mcp-grafana

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/0xteamhq-mcp-grafana/query-prometheus.md

WHAT IT DOES

What query_prometheus does on Grafana MCP Server

AI agents call query_prometheus to retrieve information from Grafana MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why query_prometheus is rated Low

This tool retrieves monitoring data from Prometheus through standard query operations. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or trigger external operations with unpredictable outcomes. The blast radius of misuse is limited to information disclosure of metrics data.

From the tool's definition Tool name 'query_prometheus' and description 'Query Prometheus using a PromQL expression. Supports both instant and range queries.' indicate data retrieval only. PromQL queries are read-only operations that fetch metrics without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_prometheus safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Grafana MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_prometheus, this is the rule to start with:

query_prometheus Allowed

query_prometheus is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_prometheus": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Grafana MCP Server, apply this rule, and every query_prometheus call is checked against it from then on.

FAQ

Questions about query_prometheus

What does the query_prometheus tool do? +

Query Prometheus using a PromQL expression. Supports both instant and range queries. It is categorised as a Read tool in the Grafana MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_prometheus? +

Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for query_prometheus: 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 Grafana MCP Server. Nothing to install.

What risk level is query_prometheus? +

query_prometheus is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_prometheus? +

Yes. Add a rate_limit block to the query_prometheus 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.

How do I block query_prometheus completely? +

Set action: deny in the PolicyLayer policy for query_prometheus. 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.

What MCP server provides query_prometheus? +

query_prometheus is provided by the Grafana MCP Server MCP server (0xteamhq/mcp-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Grafana MCP Server, and thousands of servers like it.

This server

All 43 Grafana MCP Server tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →