Pausiert einen Monitor (kein Check mehr).
AI agents invoke uptime_pause_monitor to trigger actions in Uptime Kuma. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Pausing a monitor is an operational action that triggers an external state change in the monitoring system, halting all uptime checks. This is not a simple data write (it triggers operational behavior), not destructive (it can be resumed), but it is an Execute-level action. Misuse could cause undetected outages by silencing monitoring, giving it high severity.
From the tool's definition Pausiert einen Monitor (kein Check mehr) — pauses a monitor, stopping all checks
Attacks that exploit this kind of access
Pausiert einen Monitor (kein Check mehr). It is categorised as a Execute tool in the Uptime Kuma MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Uptime Kuma MCP server in PolicyLayer and add a rule for uptime_pause_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_pause_monitor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the uptime_pause_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_pause_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_pause_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 →