query_sensor_metric · Grafana MCP Server MCP: Risk & Policy

WHAT IT DOES

What query_sensor_metric does on Grafana MCP Server

AI agents invoke query_sensor_metric 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 query_sensor_metric needs a policy

The tool executes arbitrary PromQL queries against a sensor data source. While PromQL is typically read-only for metrics retrieval, 'arbitrary' execution of queries against infrastructure can have broad blast radius implications. It falls under Execute as it runs query code dynamically against external systems, with the exact effects depending on the PromQL expression provided.

From the tool's definition Execute arbitrary PromQL against a sensor

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_sensor_metric Rate-limited

query_sensor_metric 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": {
    "query_sensor_metric": {
      "limits": [
        {
          "counter": "query_sensor_metric_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 query_sensor_metric

What does the query_sensor_metric tool do? +

Execute arbitrary PromQL against a sensor\. 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 query_sensor_metric? +

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

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

Can I rate-limit query_sensor_metric? +

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

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

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