list_prometheus_alerts

List Prometheus alerts from Grafana's Prometheus datasource proxy.

Server Mcp Grafana romaine-life/mcp-grafana
Category Read
Risk class Low
Parameters 00 required

What list_prometheus_alerts does on Mcp Grafana

AI agents call list_prometheus_alerts to retrieve information from Mcp Grafana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_prometheus_alerts needs a policy

This tool retrieves/queries alert information without side effects. It does not create, modify, delete, or execute operations—it only fetches alert data for inspection. The read-only nature of the server and the passive 'list' verb confirm the Read category. Severity is low because exposing alert metadata poses minimal direct risk; an agent cannot harm systems by merely reading alerts.

From the tool's definition Tool name 'list_prometheus_alerts' and description 'List Prometheus alerts from Grafana's Prometheus datasource proxy' indicate a retrieval operation with no modification or deletion of data. Server description emphasizes 'read-only diagnostics'.

Questions about list_prometheus_alerts

What does the list_prometheus_alerts tool do? +

List Prometheus alerts from Grafana's Prometheus datasource proxy. It is categorised as a Read tool in the Mcp Grafana MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_prometheus_alerts? +

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

What risk level is list_prometheus_alerts? +

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

Can I rate-limit list_prometheus_alerts? +

Yes. Add a rate_limit block to the list_prometheus_alerts 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 list_prometheus_alerts completely? +

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

list_prometheus_alerts is provided by the Mcp Grafana MCP server (romaine-life/mcp-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.