homelab_setup · Homelab MCP: Risk & Policy

WHAT IT DOES

What homelab_setup does on Homelab

AI agents invoke homelab_setup to trigger actions in Homelab. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why homelab_setup needs a policy

A setup wizard for a homelab management server that has 'full control' over VMs, containers, and infrastructure is likely to execute configuration steps, initialize services, or trigger external operations. Setup wizards typically write configuration, execute scripts, and modify system state. Given the blast radius of misconfiguring a Proxmox homelab environment, severity is high.

From the tool's definition 'AI-guided setup wizard for homelab-mcp' combined with server description of 'full control of a Proxmox homelab, enabling management of VMs, containers, Docker projects'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

homelab_setup Rate-limited

homelab_setup stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "homelab_setup": {
      "limits": [
        {
          "counter": "homelab_setup_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Homelab, so you can run agents against it safely.

FAQ

Questions about homelab_setup

What does the homelab_setup tool do? +

AI-guided setup wizard for homelab-mcp. It is categorised as a Execute tool in the Homelab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on homelab_setup? +

Register the Homelab MCP server in PolicyLayer and add a rule for homelab_setup: 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. Nothing to install.

What risk level is homelab_setup? +

homelab_setup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit homelab_setup? +

Yes. Add a rate_limit block to the homelab_setup 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.

How do I block homelab_setup completely? +

Set action: deny in the PolicyLayer policy for homelab_setup. 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.

What MCP server provides homelab_setup? +

homelab_setup is provided by the Homelab MCP server (nainounen/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.