Lists all available profile types in a Pyroscope datasource
AI agents call list_pyroscope_profile_types 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.
This tool queries and retrieves metadata about available Pyroscope profile types from a datasource. It performs a read-only operation that does not create, modify, delete, or execute any actions. The verb 'list' and the passive framing ('all available profile types') indicate pure data retrieval with no capability to alter system state or trigger external operations.
From the tool's definition Tool name contains 'list' and description states 'Lists all available profile types' - a retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists all available profile types in a Pyroscope datasource. 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 list_pyroscope_profile_types: 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.
list_pyroscope_profile_types 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 list_pyroscope_profile_types 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 list_pyroscope_profile_types. 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.
list_pyroscope_profile_types 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 →