delete_incident
AI agents call delete_incident to permanently remove resources in Pingera MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs permanent deletion of incidents, which cannot be undone. This qualifies as Destructive per the classification rules. While the description is empty (lowering confidence slightly), the name unambiguously indicates data deletion. Severity is high because deleting incidents removes historical monitoring and alert records that may be needed for compliance, auditing, or incident investigation.
From the tool's definition Tool name is 'delete_incident' with empty description. The verb 'delete' indicates irreversible removal of incident data from the monitoring system.
Attacks that exploit this kind of access
delete_incident. It is categorised as a Destructive tool in the Pingera MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for delete_incident: 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.
delete_incident is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_incident 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 delete_incident. 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.
delete_incident 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 →