List Grafana incidents. Allows filtering by status and optionally including drill incidents
AI agents call list_incidents 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.
This tool retrieves and filters incident data without creating, modifying, or deleting any resources. It is a straightforward query operation that has no blast radius if an AI agent calls it, even with arbitrary filter parameters. It belongs in the Read category with low severity.
From the tool's definition Tool name: list_incidents - 'list' is a read operation. Description: 'List Grafana incidents. Allows filtering by status and optionally including drill incidents' - retrieves/queries incident data with no modification or side effects.
Attacks that exploit this kind of access
List Grafana incidents. Allows filtering by status and optionally including drill incidents. It is categorised as a Read tool in the Mcp Grafana MCP Server, which means it retrieves data without modifying state.
Register the Mcp Grafana MCP server in PolicyLayer and add a rule for list_incidents: 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.
list_incidents 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 list_incidents 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 list_incidents. 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.
list_incidents is provided by the Mcp Grafana MCP server (@leval/mcp-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 →