Create a Grafana snapshot from a full dashboard payload. Supports optional expiration and external snapshot fields.
AI agents use create_snapshot to create or update resources in Mcp Grafana Npx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Grafana Npx environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | — | Custom snapshot key. Required when external is true |
name | string | — | Optional snapshot name |
expires | integer | — | Snapshot expiration in seconds (e.g. 3600 for 1 hour) |
external | boolean | — | Store snapshot on external server. Requires key and deleteKey when true |
dashboard | object | Yes | Complete dashboard model to snapshot (as returned by Grafana dashboard APIs) |
deleteKey | string | — | Secret key for deleting external snapshots. Required when external is true |
Parameters from the server's own tool schema.
This tool creates a new snapshot resource within Grafana. While snapshots are typically intended to be temporary and reversible (unlike destructive deletion), the creation of artifacts within a monitoring/observability system constitutes data modification with side effects. Snapshots expose dashboard state and can be shared, making unauthorized creation a Write-level concern.
From the tool's definition create_snapshot creates a Grafana snapshot from a dashboard payload. The description explicitly states it 'create[s]' data with optional fields for expiration and external snapshot configuration.
Attacks that exploit this kind of access
Create a Grafana snapshot from a full dashboard payload. Supports optional expiration and external snapshot fields. It is categorised as a Write tool in the Mcp Grafana Npx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_snapshot accepts 6 parameters: key, name, expires, external, dashboard, deleteKey. Required: dashboard. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Grafana Npx MCP server in PolicyLayer and add a rule for create_snapshot: 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 Npx. Nothing to install.
create_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_snapshot 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 create_snapshot. 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.
create_snapshot is provided by the Mcp Grafana Npx MCP server (mcp-grafana-npx). 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 →