list_check_groups
AI agents call list_check_groups 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.
This tool retrieves or enumerates check groups from the Pingera monitoring service. There is no indication of data modification, deletion, or execution of external operations. The empty description lowers confidence slightly, but the name itself strongly suggests a simple query/list operation typical of Read category tools. Blast radius is minimal—an AI misusing this tool can only view monitoring configuration data.
From the tool's definition Tool name 'list_check_groups' indicates retrieval of check groups data. The verb 'list' is a canonical Read operation that queries and retrieves data without modification.
Attacks that exploit this kind of access
list_check_groups. 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_check_groups: 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_check_groups 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_check_groups 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_check_groups. 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_check_groups 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 →