get_checks_in_group
AI agents call get_checks_in_group 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.
No side effects are apparent from the tool name. This retrieves or lists monitoring checks associated with a group, which is a standard read operation. The empty description reduces confidence slightly, but the naming convention and context from sibling tools strongly suggest a query/retrieval function rather than modification or execution.
From the tool's definition Tool name 'get_checks_in_group' indicates a retrieval operation. The name pattern 'get_' is consistent with read-only queries.
Attacks that exploit this kind of access
get_checks_in_group. 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 get_checks_in_group: 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.
get_checks_in_group 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_checks_in_group 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_checks_in_group. 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_checks_in_group 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 →