List all available metrics in Prometheus
AI agents call list_metrics to retrieve information from Prometheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves metadata about available metrics in a Prometheus instance. It performs no data modification, code execution, or destructive operations. The blast radius of misuse is minimal—an agent could discover metric names but cannot extract sensitive time-series data, execute queries, or modify any state. This is strictly a Read category tool.
From the tool's definition Tool name 'list_metrics' and description 'List all available metrics in Prometheus' indicate a query/discovery operation with no modification or execution of code. This is a straightforward read-only retrieval of metric names.
Attacks that exploit this kind of access
List all available metrics in Prometheus. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for list_metrics: 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 Prometheus MCP Server. Nothing to install.
list_metrics 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_metrics 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_metrics. 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_metrics is provided by the Prometheus MCP Server MCP server (jayanth-kulkarni-avesha/prometheus-mcp-server). 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 →