list_prometheus_metric_names

List metric names in a Prometheus datasource. Retrieves all metric names and filters them using regex.

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/list-prometheus-metric-names.md

What list_prometheus_metric_names does on Grafana MCP Server

AI agents call list_prometheus_metric_names 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.

Why list_prometheus_metric_names is rated Low

This tool only queries and lists metric metadata from Prometheus without executing arbitrary queries, modifying data, or triggering external operations. It is a straightforward data retrieval operation with minimal blast radius if misused—an attacker could learn what metrics exist in the system but cannot access actual metric values, modify infrastructure, or execute code.

From the tool's definition Tool description states it 'Retrieves all metric names' and 'filters them using regex'. The verb 'Retrieves' and the read-only nature of listing metric names (no datasource modification or query execution) clearly indicate a retrieval operation.

Questions about list_prometheus_metric_names

What does the list_prometheus_metric_names tool do? +

List metric names in a Prometheus datasource. Retrieves all metric names and filters them using regex. 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 list_prometheus_metric_names? +

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

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

Can I rate-limit list_prometheus_metric_names? +

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

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

list_prometheus_metric_names 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.

More on Grafana MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Grafana MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.