This record as markdown: /tools/kh0pper-crow/uptimekuma-metrics.md
What uptimekuma_metrics does on Crow
AI agents call uptimekuma_metrics 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.
Why uptimekuma_metrics is rated Low
This tool retrieves monitoring metrics from Uptime Kuma, a status page and uptime monitoring system. The action is purely observational—fetching existing data with no side effects, no modifications, and no destructive operations. It falls squarely into the Read category with low severity since metric data is typically non-sensitive operational information.
From the tool's definition Tool name 'uptimekuma_metrics' and description 'Fetch Uptime Kuma' indicate data retrieval. 'Fetch' is a read operation that queries metrics from an Uptime Kuma monitoring service without modifying state.
Attacks that exploit this kind of access
The rule that runs uptimekuma_metrics 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_metrics, this is the rule to start with:
uptimekuma_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every uptimekuma_metrics call is checked against it from then on.
Questions about uptimekuma_metrics
Fetch Uptime Kuma. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for uptimekuma_metrics: 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.
uptimekuma_metrics 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 uptimekuma_metrics 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 uptimekuma_metrics. 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.
uptimekuma_metrics 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue