Consultes as regras e diretrizes para fazer queries e interagir com o Prometheus
AI agents call context-prometheus to retrieve information from Prometheus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to provide guidance, rules, and guidelines for interacting with Prometheus—essentially a reference or documentation lookup function. It retrieves information to inform proper usage but does not itself execute queries, modify data, delete anything, or trigger external operations. The low severity reflects minimal risk even if misused, as it only retrieves instructional/reference content.
From the tool's definition Tool description states 'Consultes as regras e diretrizes para fazer queries' (Consults the rules and guidelines for making queries), indicating it retrieves configuration/reference information about how to query Prometheus.
Attacks that exploit this kind of access
Consultes as regras e diretrizes para fazer queries e interagir com o Prometheus. It is categorised as a Read tool in the Prometheus MCP Server, which means it retrieves data without modifying state.
Register the Prometheus MCP server in PolicyLayer and add a rule for context-prometheus: 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. Nothing to install.
context-prometheus 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 context-prometheus 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 context-prometheus. 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.
context-prometheus is provided by the Prometheus MCP server (mateusdata/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 →