restore_dashboard_version · Grafana MCP Server MCP

WHAT IT DOES

What restore_dashboard_version does on Grafana MCP Server

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

WHY IT NEEDS A POLICY

Why restore_dashboard_version needs a policy

This tool modifies dashboard state by reverting to a previous version. While reversible (another restore could undo it), it changes the current dashboard configuration and could affect monitoring/alerting for other users. This qualifies as Write (modifies data reversibly) rather than Destructive (since the action can be undone by restoring again).

From the tool's definition The tool name 'restore_dashboard_version' and description 'Restore a dashboard to a specific version' indicate modification of existing dashboards to a previous state. This is a reversible operation that changes dashboard configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_dashboard_version Rate-limited

restore_dashboard_version 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": {
    "restore_dashboard_version": {
      "limits": [
        {
          "counter": "restore_dashboard_version_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 Grafana MCP Server, so you can run agents against it safely.

FAQ

Questions about restore_dashboard_version

What does the restore_dashboard_version tool do? +

Restore a dashboard to a specific version. It is categorised as a Write tool in the Grafana MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on restore_dashboard_version? +

Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for restore_dashboard_version: 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 MCP Server. Nothing to install.

What risk level is restore_dashboard_version? +

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

Can I rate-limit restore_dashboard_version? +

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

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

restore_dashboard_version is provided by the Grafana MCP Server MCP server (quanticsoul4772/grafana-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.