Get a single incident by ID. Returns the full incident details
AI agents call get_incident 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 is a straightforward data retrieval operation. It queries and returns incident information by ID without creating, modifying, deleting, or executing any actions. The verb 'Get' and the passive description 'Returns' confirm read-only semantics. Severity is low because reading incident data has minimal blast radius compared to tools that modify incidents like 'create_incident' or 'add_activity_to_incident'.
From the tool's definition Tool name is 'get_incident' and description states 'Get a single incident by ID. Returns the full incident details' - purely retrieves incident data without modification or side effects.
Attacks that exploit this kind of access
Get a single incident by ID. Returns the full incident details. 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 get_incident: 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.
get_incident 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 get_incident 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 get_incident. 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.
get_incident 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 →