proxmox_create_ct · Homelab MCP: Risk & Policy

WHAT IT DOES

What proxmox_create_ct does on Homelab

AI agents invoke proxmox_create_ct 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 proxmox_create_ct needs a policy

Creating an LXC container involves allocating compute resources, storage, and networking on the Proxmox hypervisor. This is an Execute-level action (triggering external infrastructure operations) with high severity because misuse could exhaust system resources, create unauthorized environments, or be used as a pivot point for further attacks.

From the tool's definition "Create a new Debian 12 LXC container on the Proxmox node" — provisions and starts a new virtualized environment on infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

proxmox_create_ct Rate-limited

proxmox_create_ct 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": {
    "proxmox_create_ct": {
      "limits": [
        {
          "counter": "proxmox_create_ct_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 proxmox_create_ct

What does the proxmox_create_ct tool do? +

Create a new Debian 12 LXC container on the Proxmox node. 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 proxmox_create_ct? +

Register the Homelab MCP server in PolicyLayer and add a rule for proxmox_create_ct: 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 proxmox_create_ct? +

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

Can I rate-limit proxmox_create_ct? +

Yes. Add a rate_limit block to the proxmox_create_ct 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 proxmox_create_ct completely? +

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

proxmox_create_ct 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.