AI agents call list_sub_check_rule_results 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.
The 'list_sub_check_rule_results' tool appears to query or enumerate results of sub-checks (likely from AWS Managed Prometheus monitoring rules), with no indication of data modification, deletion, or execution of arbitrary operations. The 'list' verb is a strong signal for Read category. However, the empty description prevents higher confidence assessment of the exact purpose and scope.
From the tool's definition Tool name includes 'list' which indicates data retrieval without modification. Description is empty, limiting confidence.
Documented attack patterns abuse exactly the kind of access list_sub_check_rule_results gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_sub_check_rule_results:
{
"version": "1",
"default": "deny",
"tools": {
"list_sub_check_rule_results": {}
}
}list_sub_check_rule_results is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_sub_check_rule_results. 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 list_sub_check_rule_results: 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.
list_sub_check_rule_results 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 list_sub_check_rule_results 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 list_sub_check_rule_results. 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.
list_sub_check_rule_results is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.