Low Risk

list_pyroscope_profile_types

Lists all available profile types available in a specified Pyroscope datasource and time range. Returns a list of all available profile types (example profile type: "process_cpu:cpu:nanoseconds:cpu:nanoseconds"). A profile type has the following structure: <name>:<sample type>:<sample unit>:<peri...

Risk signalsBulk/mass operation — affects multiple targets

Part of the Mcp Grafana Npx server.

list_pyroscope_profile_types is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCP GRAFANA NPX →

Free to start. No card required.

AI agents call list_pyroscope_profile_types to retrieve information from Mcp Grafana Npx without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_pyroscope_profile_types only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_pyroscope_profile_types": {}
  }
}

See the full Mcp Grafana Npx policy for all 52 tools.

Get this rule live on your own Mcp Grafana Npx server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP GRAFANA NPX →

View all 52 tools →

These attack patterns abuse exactly the kind of access list_pyroscope_profile_types gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_pyroscope_profile_types only ever does what you allow.

SECURE MCP GRAFANA NPX →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_pyroscope_profile_types tool do? +

Lists all available profile types available in a specified Pyroscope datasource and time range. Returns a list of all available profile types (example profile type: "process_cpu:cpu:nanoseconds:cpu:nanoseconds"). A profile type has the following structure: <name>:<sample type>:<sample unit>:<period type>:<period unit>. Not all profile types are available for every service. If the time range is not provided, it defaults to the last hour.. It is categorised as a Read tool in the Mcp Grafana Npx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_pyroscope_profile_types? +

Register the Mcp Grafana Npx 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 Npx. Nothing to install.

What risk level is list_pyroscope_profile_types? +

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

Can I rate-limit list_pyroscope_profile_types? +

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.

How do I block list_pyroscope_profile_types completely? +

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.

What MCP server provides list_pyroscope_profile_types? +

list_pyroscope_profile_types is provided by the Mcp Grafana Npx MCP server (mcp-grafana-npx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Grafana Npx tool call.

Deterministic rules across all 52 Mcp Grafana Npx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.