Letzte Heartbeats. Mit monitor_id: letzte 24h dieses Monitors.
AI agents call uptime_get_heartbeats 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 or queries heartbeat history data with no side effects. It fits the Read category as it only fetches monitoring data. Severity is low because heartbeat/uptime statistics are non-sensitive observability data, and misuse by an AI agent would have minimal blast radius—merely reading existing status information.
From the tool's definition 'Letzte Heartbeats' (Latest heartbeats) - retrieves historical heartbeat data for a monitor. The tool queries and returns uptime statistics without modifying any data.
Attacks that exploit this kind of access
Letzte Heartbeats. Mit monitor_id: letzte 24h dieses Monitors. 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_heartbeats: 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_heartbeats 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_heartbeats 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_heartbeats. 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_heartbeats 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 →