Löscht einen Monitor permanent.
AI agents call uptime_delete_monitor to permanently remove resources in Uptime Kuma — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a monitor, which is an irreversible action that destroys data and cannot be undone. This fits the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The high severity reflects that an AI agent could permanently remove critical monitoring infrastructure by mistake, disrupting visibility into system health and uptime tracking.
From the tool's definition Tool name is 'uptime_delete_monitor' and description states 'Löscht einen Monitor permanent' (German: 'Deletes a monitor permanently'). The word 'permanent' and 'delete' clearly indicate irreversible data removal.
Attacks that exploit this kind of access
Löscht einen Monitor permanent. It is categorised as a Destructive tool in the Uptime Kuma MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Uptime Kuma MCP server in PolicyLayer and add a rule for uptime_delete_monitor: 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 Uptime Kuma. Nothing to install.
uptime_delete_monitor 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 uptime_delete_monitor 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 uptime_delete_monitor. 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.
uptime_delete_monitor is provided by the Uptime Kuma MCP server (mbay-odw/uptime-kuma-mcp-server). 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 →