// SCAN REPORT

Homelab

60 tools. 6 can modify or destroy data without limits.

6 write tools that can modify data. Rate limits recommended.

Last updated:

6 can modify or destroy data
54 read-only
60 tools total

Community server · catalogue entry verified 03/07/2026

How to control Homelab ↓

TOOL MAP

What Homelab exposes to your agents

Read (54) Write / Execute (6) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS
High Risk

The most dangerous Homelab tools

Execute · Medium ping_group Pinging all hosts in an Ansible group executes an external operation against potentially many remote systems. Execute · Medium ping_host Pinging a host via Ansible involves executing a network operation (ICMP or Ansible ping module) against a remote host. Execute · Medium ping_ping_group This tool executes an Ansible ping operation across all hosts in a group, which involves initiating network/SSH connections to remote systems. Execute · Medium ping_ping_host This tool executes a ping operation against a host, which triggers an external network operation.

6 of Homelab's 60 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Homelab

PolicyLayer is an MCP gateway — it sits between your AI agents and Homelab, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "write_mcp_file": {
    "limits": [
      {
        "counter": "write_mcp_file_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "check_container": {
    "limits": [
      {
        "counter": "check_container_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Homelab — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON HOMELAB →

Instant setup, no code required.

FULL CATALOGUE

All 60 Homelab tools

EXECUTE 5 tools
Execute ping_group Ping all hosts in an Ansible group Execute ping_host Ping a specific host by hostname from Ansible inventory Execute ping_ping_group Ping all hosts in an Ansible group Execute ping_ping_host Ping a specific host by hostname from Ansible inventory Execute ping_reload_inventory Reload Ansible inventory from disk (useful after inventory changes)
WRITE 1 tools
Write write_mcp_file Write content to an MCP file. Creates parent directories if needed. Path can be absolute or relative to MCP di
READ 54 tools
Read check_container Check if a specific container is running on a host Read docker_check_container Check if a specific container is running on a host Read docker_find_containers_by_label Find containers by label key-value pair (e.g., find traefik-enabled containers or containers with specific dom Read docker_get_all_containers Get all containers across all hosts Read docker_get_container_labels Get all labels for a specific container Read docker_get_container_stats Get CPU and memory stats for containers on a host Read docker_get_containers Get containers on a specific host (works with both Docker and Podman) Read find_containers_by_label Find containers by label key-value pair (e.g., find traefik-enabled containers or containers with specific dom Read get_all_containers Get all containers across all hosts Read get_all_groups Get a list of all groups defined in the Ansible inventory Read get_all_hosts Get a list of all hosts in the Ansible inventory with their basic information Read get_battery_runtime Get battery runtime estimates for all UPS devices Read get_claude_config Get the Claude Desktop MCP server configuration. Shows all registered MCP servers. Read get_container_labels Get all labels for a specific container Read get_container_stats Get CPU and memory stats for containers on a host Read get_docker_containers Get containers on a specific host (works with both Docker and Podman) Read get_group_details Get detailed information about a specific group including all hosts and variables Read get_host_details Get detailed information about a specific host including all variables and group memberships Read get_hosts_by_group Get all hosts that belong to a specific group Read get_inventory_summary Get a high-level summary of the inventory including counts and structure Read get_litellm_status Check LiteLLM proxy status Read get_network_clients Get all active network clients and their connections. This is cached for better performance. Read get_network_devices Get all Unifi network devices (switches, APs, gateways) with status and basic info. This is cached for better Read get_network_summary Get network overview: VLANs, device count, client count. Fast summary view. Read get_ollama_models Get models on a specific Ollama host Read get_ollama_status Check status of all Ollama instances Read get_pihole_stats Get DNS statistics from all Pi-hole instances Read get_pihole_status Check which Pi-hole instances are online Read get_power_events Check for recent power events (status changes from online to battery) Read get_ups_details Get detailed information for a specific UPS device Read get_ups_status Get status of all UPS devices across all NUT servers Read list_groups List all available Ansible groups for pinging Read list_hosts List all hosts in the Ansible inventory with their resolved IPs Read list_mcp_directory List all files and directories in the MCP development directory. Read list_mcp_servers List all MCP servers registered in Claude Desktop config with their details. Read list_ups_devices List all UPS devices configured in the inventory Read ollama_get_litellm_status Check LiteLLM proxy status Read ollama_get_models Get models on a specific Ollama host Read ollama_get_status Check status of all Ollama instances Read pihole_get_stats Get DNS statistics from all Pi-hole instances Read pihole_get_status Check which Pi-hole instances are online Read ping_all Ping all hosts in the infrastructure Read ping_list_groups List all available Ansible groups for pinging Read ping_list_hosts List all hosts in the Ansible inventory with their resolved IPs Read ping_ping_all Ping all hosts in the infrastructure Read read_mcp_file Read the contents of a specific MCP file. Provide either absolute path or relative to MCP directory. Read refresh_network_data Force refresh network data from Unifi controller (bypasses cache). Read reload_inventory Reload the inventory file from disk (useful if it has been updated) Read search_hosts Search for hosts by name pattern or by variable values Read search_mcp_files Search for files in MCP directory by name. Optionally filter by extensions. Read unifi_get_network_clients Get all active network clients and their connections. This is cached for better performance. Read unifi_get_network_devices Get all Unifi network devices (switches, APs, gateways) with status and basic info. This is cached for better Read unifi_get_network_summary Get network overview: VLANs, device count, client count. Fast summary view. Read unifi_refresh_network_data Force refresh network data from Unifi controller (bypasses cache).
FAQ

Questions about Homelab

How do I prevent bulk modifications through Homelab? +

The Homelab server has 1 write tools including write_mcp_file. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Homelab.

How many tools does the Homelab MCP server expose? +

60 tools across 2 categories: Read, Write. 54 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Homelab? +

Register the Homelab MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Homelab tool call.

Deterministic rules across all 60 Homelab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON HOMELAB →

Instant setup, no code required.

60 Homelab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.