List Prometheus scrape targets with health status and last scrape time.
AI agents call prom_targets to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward data retrieval operation (list) from Prometheus, returning observability metadata about monitoring targets. There are no side effects, no code execution, no data modification, and no destructive or financial implications. The blast radius of misuse is minimal — an agent could only gain visibility into monitoring infrastructure configuration, which is low-severity exposure.
From the tool's definition Tool description states 'List Prometheus scrape targets with health status and last scrape time' — a read-only operation that retrieves and queries monitoring metadata without modifying or executing anything.
Attacks that exploit this kind of access
List Prometheus scrape targets with health status and last scrape time. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for prom_targets: 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_targets 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 prom_targets 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_targets. 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_targets 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 →