Searches relevant Tempo datasources for slow requests and returns the results
AI agents call find_slow_requests to retrieve information from Mcp Grafana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search operation against Tempo datasources to find slow requests and return matching data. This is a read-only retrieval operation analogous to a database query that does not create, modify, delete, or execute external operations. The verb 'Searches' and 'returns the results' indicate passive data retrieval.
From the tool's definition Tool description states it 'Searches relevant Tempo datasources for slow requests and returns the results' — a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Searches relevant Tempo datasources for slow requests and returns the results. It is categorised as a Read tool in the Mcp Grafana MCP Server, which means it retrieves data without modifying state.
Register the Mcp Grafana 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 Mcp Grafana. Nothing to install.
find_slow_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
find_slow_requests is provided by the Mcp Grafana MCP server (@leval/mcp-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →