find_slow_requests

Searches relevant Tempo datasources for slow requests and returns the results

SERVERGrafana MCP Server SOURCE0xteamhq/mcp-grafana

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/0xteamhq-mcp-grafana/find-slow-requests.md

WHAT IT DOES

What find_slow_requests does on Grafana MCP Server

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

RISK

Why find_slow_requests is rated Low

This tool queries Tempo (a distributed tracing datasource) to retrieve slow request traces. While it is read-only, the severity is medium rather than low because: (1) tracing data can reveal sensitive information about system internals, performance characteristics, and potentially user-facing latencies; (2) an AI agent with misuse could extract data about system weaknesses or private operations; (3) it fits the…

From the tool's definition Tool description states it 'Searches relevant Tempo datasources for slow requests and returns the results' — this is a retrieval/query operation with no modification or side effects. The verb 'Searches' and 'returns' indicate read-only behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_slow_requests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Grafana MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_slow_requests, this is the rule to start with:

find_slow_requests Allowed

find_slow_requests is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_slow_requests": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Grafana MCP Server, apply this rule, and every find_slow_requests call is checked against it from then on.

FAQ

Questions about find_slow_requests

What does the find_slow_requests tool do? +

Searches relevant Tempo datasources for slow requests and returns the results. 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 find_slow_requests? +

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

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

Can I rate-limit find_slow_requests? +

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

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

find_slow_requests is provided by the Grafana MCP Server MCP server (0xteamhq/mcp-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Grafana MCP Server, and thousands of servers like it.

This server

All 43 Grafana MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →