list_checks
AI agents call list_checks to retrieve information from Pingera MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations retrieve and query data without modifying, deleting, or executing external operations. The monitoring context (Pingera) and naming convention confirm this is a read-only query. Low severity since listing checks poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_checks' with no description provided; sibling tools include create_check, create_alert, add_incident_update suggesting a monitoring service API; the 'list_' prefix strongly indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
list_checks. It is categorised as a Read tool in the Pingera MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pingera MCP Server 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 Pingera MCP Server. 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 Pingera MCP Server MCP server (pingera/pingera-mcp). 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 →