Delete a heartbeat monitor and all its ping history. This action is IRREVERSIBLE. Safety: Pass confirm=true to actually delete.
Part of the PingZen Uptime Monitoring server.
Free to start. No card required.
AI agents may call delete_heartbeat to permanently remove or destroy resources in PingZen Uptime Monitoring. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call delete_heartbeat in a loop, permanently destroying resources in PingZen Uptime Monitoring. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"delete_heartbeat"
]
}See the full PingZen Uptime Monitoring policy for all 44 tools.
These attack patterns abuse exactly the kind of access delete_heartbeat gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Delete a heartbeat monitor and all its ping history. This action is IRREVERSIBLE. Safety: Pass confirm=true to actually delete.. It is categorised as a Destructive tool in the PingZen Uptime Monitoring MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PingZen Uptime Monitoring 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 PingZen Uptime Monitoring. 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 PingZen Uptime Monitoring MCP server (pingzen/uptime-monitoring). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 44 PingZen Uptime Monitoring tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.