Get scrape target information
AI agents call prom_targets 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 information about Prometheus scrape targets—configuration and status data—without modifying, executing, or deleting anything. It is analogous to a 'list' or 'get' operation. The blast radius of misuse is minimal, as an AI agent cannot cause harm by reading target metadata.
From the tool's definition Tool name 'prom_targets' and description 'Get scrape target information' indicate a retrieval operation. The verb 'Get' and context of Prometheus monitoring (querying metrics, discovering data) establish this as a read-only query of configuration metadata.
Attacks that exploit this kind of access
Get scrape target information. 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 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 Prometheus MCP Server. 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 Prometheus MCP Server MCP server (yanmxa/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 →