query_prometheus
AI agents call query_prometheus to retrieve information from Mcp Read Only Grafana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context indicate this is a query operation against Prometheus for retrieving monitoring data. Despite the empty description reducing confidence slightly, the naming convention and server's documented read-only posture strongly suggest a non-mutating data retrieval operation. No write, delete, execute, or financial operations are implied.
From the tool's definition Tool name 'query_prometheus' and server description states 'read-only access by default'. Prometheus is a monitoring system; querying it retrieves metrics data without side effects.
Attacks that exploit this kind of access
query_prometheus. It is categorised as a Read tool in the Mcp Read Only Grafana MCP Server, which means it retrieves data without modifying state.
Register the Mcp Read Only Grafana 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 Mcp Read Only Grafana. Nothing to install.
query_prometheus is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
query_prometheus is provided by the Mcp Read Only Grafana MCP server (lukleh/mcp-read-only-grafana). 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 →