List every host in the fleet with headline vitals (hub listed first). Returns the roster: name, online status, OS, CPU/RAM load, fullest disk and any OS-upgrade/reboot hint per host. Start here, then drill in with get_host.
AI agents call list_hosts to retrieve information from HomeLab Monitor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward query operation that retrieves and displays system information. It performs no modifications, deletions, code execution, or financial operations. The blast radius of misuse is minimal—an AI agent querying host status cannot cause harm beyond consuming API resources. Classified as Read with low severity.
From the tool's definition Tool name 'list_hosts' and description 'List every host in the fleet with headline vitals' indicates data retrieval without modification. Returns read-only roster information: name, online status, OS, CPU/RAM load, disk usage, and upgrade hints.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list_hosts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeLab Monitor, and nothing reaches the server without passing your rules. This is the rule we recommend for list_hosts:
{
"version": "1",
"default": "deny",
"tools": {
"list_hosts": {}
}
}list_hosts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List every host in the fleet with headline vitals (hub listed first). Returns the roster: name, online status, OS, CPU/RAM load, fullest disk and any OS-upgrade/reboot hint per host. Start here, then drill in with get_host. It is categorised as a Read tool in the HomeLab Monitor MCP Server, which means it retrieves data without modifying state.
Register the HomeLab Monitor MCP server in PolicyLayer and add a rule for list_hosts: 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 HomeLab Monitor. Nothing to install.
list_hosts 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 list_hosts 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 list_hosts. 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.
list_hosts is provided by the HomeLab Monitor MCP server (sikamikanikobg/homelab-monitor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 HomeLab Monitor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 HomeLab Monitor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.