devbox_project_deploy · Homelab MCP: Risk & Policy

WHAT IT DOES

What devbox_project_deploy does on Homelab

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

This tool executes a sequence of shell commands (git pull, docker compose pull, docker compose up -d) that trigger external operations with side effects. While individually these might seem like routine deployment steps, the combination enables execution of arbitrary code from git repositories and Docker images, plus starting/modifying running services.

From the tool's definition Tool performs git pull, docker compose pull, and docker compose up -d commands, which execute external operations and scripts whose effects depend on project contents and configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

devbox_project_deploy Rate-limited

devbox_project_deploy 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": {
    "devbox_project_deploy": {
      "limits": [
        {
          "counter": "devbox_project_deploy_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 devbox_project_deploy

What does the devbox_project_deploy tool do? +

Deploy a project: git pull, docker compose pull, docker compose up -d, then show status. 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 devbox_project_deploy? +

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

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

Can I rate-limit devbox_project_deploy? +

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

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

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