List all configured Prometheus tenants
AI agents call list_tenants 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.
This tool retrieves and enumerates tenant configuration information. It performs a read-only operation that queries existing state without creating, modifying, deleting, or executing any actions. The low severity reflects that listing tenant names poses minimal risk even if invoked inappropriately by an agent, as it only exposes organizational metadata about available monitoring endpoints.
From the tool's definition Tool name is 'list_tenants' and description states 'List all configured Prometheus tenants' — this is a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
List all configured Prometheus tenants. 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_tenants: 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_tenants 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_tenants 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_tenants. 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_tenants 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 →