explore_sensor_metrics

List all available Prometheus metric names on a sensor, grouped by subsystem.

Server Grafana MCP Server quanticsoul4772/grafana-mcp
Category Read
Risk class Low
Parameters 00 required

What explore_sensor_metrics does on Grafana MCP Server

AI agents call explore_sensor_metrics to retrieve information from Grafana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why explore_sensor_metrics needs a policy

This is a straightforward metric discovery/exploration tool that queries Prometheus for available metrics. It has no side effects, makes no modifications, and does not execute code or delete data. It falls squarely into the Read category as a retrieval operation. The blast radius of misuse is minimal—an attacker could learn about available metrics but cannot affect system state.

From the tool's definition The tool 'explore_sensor_metrics' performs a 'List' operation to retrieve and enumerate available Prometheus metric names without modifying, executing, or deleting anything. The description explicitly states it lists metrics and groups them by subsystem.

Questions about explore_sensor_metrics

What does the explore_sensor_metrics tool do? +

List all available Prometheus metric names on a sensor, grouped by subsystem. It is categorised as a Read tool in the Grafana MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on explore_sensor_metrics? +

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

explore_sensor_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit explore_sensor_metrics? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.