get_check_results
AI agents call get_check_results 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.
The tool retrieves or queries existing monitoring data from Pingera without creating, modifying, or deleting resources. This is a read-only operation typical of monitoring dashboards and health status queries. No side effects are expected. Confidence is moderate-high despite empty description because the tool name and server context are informative.
From the tool's definition Tool name 'get_check_results' indicates retrieval of monitoring check results with no mutation. Description is empty, but naming convention and context within a monitoring service (alongside tools like 'create_check', 'add_incident_update') strongly suggest…
Attacks that exploit this kind of access
get_check_results. 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_check_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 Pingera MCP Server. Nothing to install.
get_check_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 get_check_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 get_check_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.
get_check_results 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 →