list_incidents
AI agents call list_incidents 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 return data without side effects. Monitoring incident data is informational only; reading it poses minimal risk even if exposed to an agent. No data modification, deletion, code execution, or financial operations are involved.
From the tool's definition Tool name 'list_incidents' indicates retrieval of incident data with no modification capability. The empty description is uninformative, but the name and context (sibling tools like 'add_incident_update' and 'create_alert' handle writes) confirm this is a…
Attacks that exploit this kind of access
list_incidents. 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_incidents: 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_incidents 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_incidents 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_incidents. 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_incidents 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 →