Voll-Details zu einem Monitor inkl. Settings, Notifications, Tags.
AI agents call uptime_get_monitor 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 queries detailed information about a monitor including its settings, notifications, and tags. It performs no side effects, does not create, modify, or delete data, and does not execute external operations. It is a straightforward data retrieval operation, placing it firmly in the Read category.
From the tool's definition Tool name 'uptime_get_monitor' and description 'Voll-Details zu einem Monitor inkl. Settings, Notifications, Tags' (Full details of a monitor including settings, notifications, tags) indicates retrieval of monitor configuration and status information without…
Attacks that exploit this kind of access
Voll-Details zu einem Monitor inkl. Settings, Notifications, Tags. 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_get_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_get_monitor 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_get_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_get_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_get_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 →