Execute a query across all configured tenants
AI agents invoke execute_query_all_tenants to trigger actions in Prometheus MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs PromQL queries dynamically across multiple tenants, which constitutes code execution (the queries are evaluated by Prometheus engines with effects dependent on query arguments). While read-only in nature, PromQL queries can be computationally expensive and resource-intensive, affecting system performance. The multi-tenant scope amplifies blast radius.
From the tool's definition Tool name 'execute_query' combined with description stating it 'Execute[s] a query across all configured tenants' indicates runtime code execution.
Attacks that exploit this kind of access
Execute a query across all configured tenants. It is categorised as a Execute tool in the Prometheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for execute_query_all_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.
execute_query_all_tenants is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_query_all_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 execute_query_all_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.
execute_query_all_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 →