Run the SlowRequests check via Sift and return the analysis result.
AI agents invoke find_slow_requests to trigger actions in Grafana FastMCP 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.
The tool executes an analysis check via Sift, an external system. This is not a simple read/query of existing data but rather triggering an external operation whose effects depend on arguments. It likely reads and analyzes data, but the 'run' verb and external system invocation classify it as Execute. Severity is medium as misuse could trigger unintended load or analysis operations but doesn't modify or delete data.
From the tool's definition 'Run the SlowRequests check via Sift' — explicitly runs/executes a check/analysis operation via an external system (Sift)
Documented attack patterns abuse exactly the kind of access find_slow_requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grafana FastMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_slow_requests:
{
"version": "1",
"default": "deny",
"tools": {
"find_slow_requests": {
"limits": [
{
"counter": "find_slow_requests_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}find_slow_requests 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.
Free to start. No card required.
Run the SlowRequests check via Sift and return the analysis result. It is categorised as a Execute tool in the Grafana FastMCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Grafana FastMCP 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 FastMCP Server. Nothing to install.
find_slow_requests is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 Grafana FastMCP Server MCP server (sandersouza/grafanafastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Grafana FastMCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 Grafana FastMCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.