save_dashboard · Mcp Read Only Grafana MCP: Risk & Policy

WHAT IT DOES

What save_dashboard does on Mcp Read Only Grafana

AI agents use save_dashboard to create or update resources in Mcp Read Only Grafana — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Read Only Grafana environment.

WHY IT NEEDS A POLICY

Why save_dashboard needs a policy

The tool name 'save_dashboard' strongly suggests persisting dashboard configuration changes, which is a reversible Write operation that modifies Grafana state. Although the description is empty, the server's explicit mention of 'separate write-capable command for mutations' and the presence of sibling tools like create_* and delete_* confirms this server exposes mutation capabilities.

From the tool's definition Tool name 'save_dashboard' combined with server context indicating 'write-capable command for mutations' and sibling destructive/write tools (create_*, delete_*). Description is empty, which reduces confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_dashboard Rate-limited

save_dashboard stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_dashboard": {
      "limits": [
        {
          "counter": "save_dashboard_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Read Only Grafana, so you can run agents against it safely.

FAQ

Questions about save_dashboard

What does the save_dashboard tool do? +

save_dashboard. It is categorised as a Write tool in the Mcp Read Only Grafana MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_dashboard? +

Register the Mcp Read Only Grafana MCP server in PolicyLayer and add a rule for save_dashboard: 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.

What risk level is save_dashboard? +

save_dashboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_dashboard? +

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

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

save_dashboard 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.