Return all allowlisted monitoring checks available to the MCP server.
AI agents call list_checks to retrieve information from MCP Prometheus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available monitoring checks without modifying, executing, deleting, or creating any data. It is a read-only operation that provides information about the server's monitoring capabilities. The low severity reflects minimal blast radius—an agent could at worst learn about available checks, which is informational only.
From the tool's definition Tool name 'list_checks' and description 'Return all allowlisted monitoring checks available' indicates a retrieval operation with no side effects. The verb 'return' and 'list' are consistent with querying/reading capabilities.
Attacks that exploit this kind of access
Return all allowlisted monitoring checks available to the MCP server. It is categorised as a Read tool in the MCP Prometheus MCP Server, which means it retrieves data without modifying state.
Register the MCP Prometheus MCP server in PolicyLayer and add a rule for list_checks: 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 MCP Prometheus. Nothing to install.
list_checks 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_checks 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_checks. 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_checks is provided by the MCP Prometheus MCP server (yeonkyu-git/mcp-prometheus-loki). 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 →