delete_heartbeat
AI agents call delete_heartbeat 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 'delete_' action prefix clearly signals a destructive operation that cannot be undone. Although the description is empty (lowering confidence slightly), the tool name unambiguously indicates deletion of a heartbeat resource. This is categorized as Destructive rather than Write because heartbeat deletion is irreversible and removes configured monitoring infrastructure.
From the tool's definition Tool name is 'delete_heartbeat' with no description provided. The prefix 'delete_' indicates an irreversible deletion operation. In a monitoring service context, deleting a heartbeat check would remove a configured monitoring probe permanently.
Attacks that exploit this kind of access
delete_heartbeat. 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_heartbeat: 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_heartbeat 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_heartbeat 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_heartbeat. 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_heartbeat 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.
delete_heartbeat is one line of Pingera MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →