Retrieve alerting and recording rules that are currently loaded.
AI agents call get_rules 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 alerting and recording rules from Prometheus, which is a query operation with no side effects. It does not create, modify, delete, or execute any operations—it only fetches and returns data. The blast radius of misuse is minimal, as an attacker could only gain visibility into the alert rules configured in the system, not cause harm or trigger alerts directly.
From the tool's definition Tool name 'get_rules' and description 'Retrieve alerting and recording rules that are currently loaded' indicate a read-only operation that queries and returns existing rule data without modification.
Attacks that exploit this kind of access
Retrieve alerting and recording rules that are currently loaded. 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 get_rules: 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.
get_rules 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 get_rules 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 get_rules. 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.
get_rules is provided by the Prometheus MCP Server MCP server (kakao-yanoo-kim/prometheus-mcp-server-py). 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 →