create_mute_timing · Mcp Read Only Grafana MCP

WHAT IT DOES

What create_mute_timing does on Mcp Read Only Grafana

AI agents use create_mute_timing 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 create_mute_timing needs a policy

Creating a mute timing rule modifies Grafana's alert notification behavior by creating a new configuration. This is reversible (the rule can be deleted via delete_mute_timing), so it is Write rather than Destructive.

From the tool's definition Tool name is 'create_mute_timing' indicating creation of a mute timing configuration. The server description mentions 'a separate write-capable command for mutations.' The sibling tools include destructive operations (delete_*) and other write operations…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_mute_timing Rate-limited

create_mute_timing 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": {
    "create_mute_timing": {
      "limits": [
        {
          "counter": "create_mute_timing_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 create_mute_timing

What does the create_mute_timing tool do? +

create_mute_timing. 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 create_mute_timing? +

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

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

Can I rate-limit create_mute_timing? +

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

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

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