fetch_pyroscope_profile

Fetches a profile from a Pyroscope data source for a given time range

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/fetch-pyroscope-profile.md

WHAT IT DOES

What fetch_pyroscope_profile does on Grafana MCP Server

AI agents call fetch_pyroscope_profile 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 fetch_pyroscope_profile is rated Low

This tool retrieves profiling data from Pyroscope, a performance profiling backend. Fetching/querying monitoring and profiling data is a non-destructive read operation with no capability to modify, delete, or execute arbitrary code. The blast radius if misused is limited to information disclosure of performance metrics that are typically intended to be observable by authorized users.

From the tool's definition Tool name 'fetch_pyroscope_profile' and description 'Fetches a profile from a Pyroscope data source for a given time range' indicate data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fetch_pyroscope_profile 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 fetch_pyroscope_profile, this is the rule to start with:

fetch_pyroscope_profile Allowed

fetch_pyroscope_profile 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": {
    "fetch_pyroscope_profile": {}
  }
}

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 fetch_pyroscope_profile call is checked against it from then on.

FAQ

Questions about fetch_pyroscope_profile

What does the fetch_pyroscope_profile tool do? +

Fetches a profile from a Pyroscope data source for a given time range. 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 fetch_pyroscope_profile? +

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

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

Can I rate-limit fetch_pyroscope_profile? +

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

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

fetch_pyroscope_profile 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 →