get_dashboard_panels
AI agents call get_dashboard_panels 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 'get_dashboard_panels' strongly suggests a retrieval operation that queries and returns dashboard panel information without modifying state. This aligns with the server's stated read-only design for this particular tool. While the server hosts write and destructive operations on other tools, this specific tool appears designed for safe data retrieval.
From the tool's definition Tool name 'get_dashboard_panels' indicates retrieval of dashboard panel data. Server description emphasizes 'read-only access by default'. Tool lacks destructive verbs (delete, drop) and mutation capabilities.
Attacks that exploit this kind of access
get_dashboard_panels. 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 get_dashboard_panels: 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.
get_dashboard_panels 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_dashboard_panels 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_dashboard_panels. 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_dashboard_panels 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 →