// SCAN REPORT

Uptime Kuma

15 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

4 can modify or destroy data

11 read-only

15 tools total

Community server · catalogue entry verified 02/07/2026

How to control Uptime Kuma ↓

TOOL MAP

What Uptime Kuma exposes to your agents

Read (11) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Uptime Kuma tools

Destructive · High uptime_delete_monitor This tool permanently deletes a monitor, which is an irreversible action that destroys data and cannot be undone. Execute · High uptime_pause_monitor Pausing a monitor is an operational action that triggers an external state change in the monitoring system, halting all uptime checks. Write · Medium uptime_add_monitor Creating a new monitor is a write operation that modifies the monitoring system's state by adding a new tracked resource. Write · Medium uptime_resume_monitor This tool resumes/reactivates a previously paused monitor.

4 of Uptime Kuma's 15 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Uptime Kuma

PolicyLayer is an MCP gateway — it sits between your AI agents and Uptime Kuma, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "uptime_delete_monitor": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "uptime_add_monitor": {
    "limits": [
      {
        "counter": "uptime_add_monitor_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "uptime_get_avg_response": {
    "limits": [
      {
        "counter": "uptime_get_avg_response_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Uptime Kuma — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON UPTIME KUMA →

Instant setup, no code required.

FULL CATALOGUE

All 15 Uptime Kuma tools

DESTRUCTIVE 1 tools

Destructive uptime_delete_monitor Löscht einen Monitor permanent.

EXECUTE 1 tools

Execute uptime_pause_monitor Pausiert einen Monitor (kein Check mehr).

WRITE 2 tools

Write uptime_add_monitor Legt einen neuen Monitor an. type: http (HTTP-GET auf URL) / Write uptime_resume_monitor Reaktiviert einen pausierten Monitor.

READ 11 tools

Read uptime_get_avg_response Durchschnittliche Antwortzeit je Monitor. Read uptime_get_heartbeats Letzte Heartbeats. Mit monitor_id: letzte 24h dieses Monitors. Read uptime_get_info Server-Info (Version, Latency, Primary-Base-URL). Read uptime_get_monitor Voll-Details zu einem Monitor inkl. Settings, Notifications, Tags. Read uptime_get_status_page Voll-Details einer Status-Page (Slug = URL-Pfad). Read uptime_get_uptime_stats Aktuelle Uptime-Prozent-Werte je Monitor (24h / 30d). Read uptime_list_maintenances Listet konfigurierte Maintenance-Fenster. Read uptime_list_monitors Listet alle konfigurierten Monitore mit Type, URL, Status. Read uptime_list_notifications Listet alle konfigurierten Notification-Channels (Discord, Telegram, ntfy, …). Read uptime_list_status_pages Listet alle Status-Pages (Public Dashboards). Read uptime_list_tags Listet alle Tags.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Uptime Kuma

Can an AI agent delete data through the Uptime Kuma MCP server? +

Yes. The Uptime Kuma server exposes 1 destructive tools including uptime_delete_monitor. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Uptime Kuma? +

The Uptime Kuma server has 2 write tools including uptime_add_monitor, uptime_resume_monitor. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Uptime Kuma.

How many tools does the Uptime Kuma MCP server expose? +

15 tools across 3 categories: Destructive, Read, Write. 11 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Uptime Kuma? +

Register the Uptime Kuma MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Uptime Kuma tool call.

Deterministic rules across all 15 Uptime Kuma tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON UPTIME KUMA →

Instant setup, no code required.

15 Uptime Kuma tools catalogued and risk-classified — across an index of 43,000+ MCP servers.