Critical-risk tools in PingZen Uptime Monitoring
6 of the 44 tools in PingZen Uptime Monitoring are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete_alertDestructive 4/5Delete an alert rule. Pass confirm=true to confirm deletion.
-
delete_heartbeatDestructive 4/5Delete a heartbeat monitor and all its ping history. This action is IRREVERSIBLE. Safety: Pass confirm=true to actually delete.
-
delete_monitorDestructive 4/5Delete a monitor and all its data (check results, alerts, incidents). This action is IRREVERSIBLE. Safety: You must pass confirm=true to actually delete. Without it, returns a ...
-
delete_monitor_groupDestructive 4/5Delete a monitor group. Monitors are NOT deleted, only ungrouped. Pass confirm=true to confirm deletion.
-
delete_telegram_groupDestructive 4/5Unlink a Telegram group. The bot stays in the group, but alerts will no longer be sent to it. Pass confirm=true to confirm.
-
remove_status_page_monitorDestructive 4/5Remove a monitor from a status page.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on PingZen Uptime Monitoring
Enforce policy on PingZen Uptime Monitoring
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init