homelab_health
Return a compact health summary for Homepage, Grafana, Uptime Kuma, and Prometheus.
This record as markdown: /tools/mcp-control-plane/homelab-health.md
What homelab_health does on Mcp Control Plane
AI agents call homelab_health to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why homelab_health is rated Low
This tool retrieves and aggregates monitoring data from observability infrastructure. It performs a read-only query operation with no side effects, no data modification, no code execution, and no irreversible actions. The blast radius of misuse is minimal—worst case an agent repeatedly queries the endpoint, causing minor resource consumption. This is a classic Read category tool.
From the tool's definition Tool name 'homelab_health' and description 'Return a compact health summary' indicate a retrieval operation that queries status information from monitoring systems (Homepage, Grafana, Uptime Kuma, Prometheus) without modifying any state.
Attacks that exploit this kind of access
The rule that runs homelab_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For homelab_health, this is the rule to start with:
homelab_health 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 Mcp Control Plane, apply this rule, and every homelab_health call is checked against it from then on.
Questions about homelab_health
Return a compact health summary for Homepage, Grafana, Uptime Kuma, and Prometheus. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for homelab_health: 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 Mcp Control Plane. Nothing to install.
homelab_health 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 homelab_health 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 homelab_health. 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.
homelab_health is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue