Listet alle Status-Pages (Public Dashboards).
AI agents call uptime_list_status_pages to retrieve information from Uptime Kuma without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates status pages from Uptime Kuma. It performs no state changes, does not execute code, does not delete data, and does not involve financial operations. The blast radius of misuse is minimal—an attacker could only discover what status pages exist, which is typically non-sensitive metadata. Classification as Read is appropriate.
From the tool's definition Tool name 'uptime_list_status_pages' and description 'Listet alle Status-Pages (Public Dashboards)' indicate a list/retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
Listet alle Status-Pages (Public Dashboards). It is categorised as a Read tool in the Uptime Kuma MCP Server, which means it retrieves data without modifying state.
Register the Uptime Kuma MCP server in PolicyLayer and add a rule for uptime_list_status_pages: 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_list_status_pages 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_list_status_pages 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_list_status_pages. 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_list_status_pages 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 →