diagnose_drops · Grafana MCP Server MCP: Risk & Policy

WHAT IT DOES

What diagnose_drops does on Grafana MCP Server

AI agents invoke diagnose_drops to trigger actions in Grafana MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why diagnose_drops needs a policy

This tool executes a diagnostic process against infrastructure (sensors), which qualifies as Execute because it runs operations whose side effects depend on arguments (which sensor, what diagnostics). While diagnostics are typically read-like, 'comprehensive diagnostic battery' suggests active probing that could affect system state or generate significant load.

From the tool's definition Tool performs diagnostic operations against a sensor ('Run a comprehensive diagnostic battery'). The action triggers external operations whose effects depend on what sensor is targeted and what diagnostics are executed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

diagnose_drops Rate-limited

diagnose_drops stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "diagnose_drops": {
      "limits": [
        {
          "counter": "diagnose_drops_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 diagnose_drops

What does the diagnose_drops tool do? +

Run a comprehensive diagnostic battery against a sensor to identify where drops are occurring and why. It is categorised as a Execute tool in the Grafana MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on diagnose_drops? +

Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for diagnose_drops: 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 diagnose_drops? +

diagnose_drops is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit diagnose_drops? +

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

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

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