sensor_status

Get live performance snapshot for a sensor: Gbps, kpps, klogps, drop rates,

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

What sensor_status does on Grafana MCP Server

AI agents call sensor_status 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 sensor_status needs a policy

This tool retrieves real-time monitoring data about sensor performance. The verb 'Get' and the reference to obtaining a 'snapshot' of metrics are characteristic of read-only operations. There is no indication of state modification, code execution, data deletion, or financial operations. The tool enables visibility into system performance but does not change any underlying data or trigger external actions.

From the tool's definition Tool name 'sensor_status' and description 'Get live performance snapshot' indicate a retrieval operation that queries sensor metrics (Gbps, kpps, klogps, drop rates) without modifying state.

Questions about sensor_status

What does the sensor_status tool do? +

Get live performance snapshot for a sensor: Gbps, kpps, klogps, drop rates,. 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 sensor_status? +

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

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

Can I rate-limit sensor_status? +

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

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

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