AI agents call uptime_status to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and displays status information from an Uptime Kuma monitoring system. It has no side effects, does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an AI agent querying this tool could only gain visibility into current service status. No remediation, control, or resource management actions are enabled by this tool alone.
From the tool's definition Tool description states 'List all Uptime Kuma monitors with their up/down status and latency' - a read-only query operation that retrieves monitoring data without modifying any state or triggering actions.
Attacks that exploit this kind of access
List all Uptime Kuma monitors with their up/down status and latency. Shows any currently down services first. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for uptime_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 Homelab. Nothing to install.
uptime_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the uptime_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.
Set action: deny in the PolicyLayer policy for uptime_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.
uptime_status is provided by the Homelab MCP server (nainounen/homelab-mcp). 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 →