Execute instant or range PromQL queries against Prometheus.
AI agents invoke prom_query to trigger actions in RedisNexus. 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.
The tool explicitly executes PromQL queries against Prometheus. While typical PromQL is read-only for metrics, 'execute' of arbitrary queries against a production monitoring system carries medium-to-high risk — a misconfigured or malicious query could cause high load on Prometheus or expose sensitive operational metrics. The word 'Execute' in the description confirms the Execute category, which ranks above Read.
From the tool's definition "Execute instant or range PromQL queries against Prometheus"
Attacks that exploit this kind of access
Execute instant or range PromQL queries against Prometheus. It is categorised as a Execute tool in the RedisNexus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RedisNexus MCP server in PolicyLayer and add a rule for prom_query: 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 RedisNexus. Nothing to install.
prom_query 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 prom_query 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 prom_query. 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.
prom_query is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). 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 →