devbox_exec · Homelab MCP: Risk & Policy

WHAT IT DOES

What devbox_exec does on Homelab

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

This tool runs shell commands on a remote system via SSH. Even with a blocklist of dangerous commands, shell execution is inherently in the Execute category—the effects depend entirely on the arguments provided (which commands are executed).

From the tool's definition Execute a shell command on the devbox via SSH. Dangerous commands are blocked.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

devbox_exec Rate-limited

devbox_exec 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_exec": {
      "limits": [
        {
          "counter": "devbox_exec_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_exec

What does the devbox_exec tool do? +

Execute a shell command on the devbox via SSH. Dangerous commands are blocked. 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_exec? +

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

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

Can I rate-limit devbox_exec? +

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

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

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