Return configured Prometheus environments and their base URLs.
AI agents call list_environments to retrieve information from MCP Prometheus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and lists existing Prometheus environment configurations. It has no side effects, does not modify any data, and does not trigger any operations. It is a straightforward read operation that returns metadata about the monitoring infrastructure.
From the tool's definition Tool name 'list_environments' and description 'Return configured Prometheus environments and their base URLs' indicates a query operation that retrieves configuration information without modifying or executing any operations.
Attacks that exploit this kind of access
Return configured Prometheus environments and their base URLs. It is categorised as a Read tool in the MCP Prometheus MCP Server, which means it retrieves data without modifying state.
Register the MCP Prometheus MCP server in PolicyLayer and add a rule for list_environments: 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 Prometheus. Nothing to install.
list_environments 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_environments 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_environments. 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_environments is provided by the MCP Prometheus MCP server (yeonkyu-git/mcp-prometheus-loki). 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 →