uptimekuma_status

Check whether Uptime Kuma is reachable on the configured URL. Returns the HTTP status of the entry page and the base URL. No credentials required.

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/uptimekuma-status.md

WHAT IT DOES

What uptimekuma_status does on Crow

AI agents call uptimekuma_status to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why uptimekuma_status is rated Low

This tool performs a passive health check of an Uptime Kuma instance by querying HTTP status. It retrieves information (HTTP status codes) without creating, modifying, executing, or deleting anything. The operation is read-only with no side effects, placing it squarely in the Read category.

From the tool's definition Tool description states it 'Check[s] whether Uptime Kuma is reachable' and 'Returns the HTTP status of the entry page and the base URL.' The description explicitly notes 'No credentials required,' indicating a simple status check with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uptimekuma_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uptimekuma_status, this is the rule to start with:

uptimekuma_status Allowed

uptimekuma_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "uptimekuma_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every uptimekuma_status call is checked against it from then on.

FAQ

Questions about uptimekuma_status

What does the uptimekuma_status tool do? +

Check whether Uptime Kuma is reachable on the configured URL. Returns the HTTP status of the entry page and the base URL. No credentials required. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on uptimekuma_status? +

Register the Crow MCP server in PolicyLayer and add a rule for uptimekuma_status: 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 Crow. Nothing to install.

What risk level is uptimekuma_status? +

uptimekuma_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit uptimekuma_status? +

Yes. Add a rate_limit block to the uptimekuma_status 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.

How do I block uptimekuma_status completely? +

Set action: deny in the PolicyLayer policy for uptimekuma_status. 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.

What MCP server provides uptimekuma_status? +

uptimekuma_status is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →