Retrieve the full details for a Grafana incident by ID.
AI agents call get_incident to retrieve information from Grafana FastMCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries incident data from Grafana without modifying, creating, deleting, or executing any operations. It is purely informational access to existing incident records, making it a Read category tool with low severity since unauthorized access to incident metadata poses minimal risk compared to write, execution, or destructive operations.
From the tool's definition Tool name and description: 'Retrieve the full details for a Grafana incident by ID.' The verb 'retrieve' and action of fetching incident details indicate a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_incident gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grafana FastMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_incident:
{
"version": "1",
"default": "deny",
"tools": {
"get_incident": {}
}
}get_incident is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the full details for a Grafana incident by ID. It is categorised as a Read tool in the Grafana FastMCP Server MCP Server, which means it retrieves data without modifying state.
Register the Grafana FastMCP Server 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 Grafana FastMCP Server. 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 Grafana FastMCP Server MCP server (sandersouza/grafanafastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Grafana FastMCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 Grafana FastMCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.