devbox_git · Homelab MCP: Risk & Policy

WHAT IT DOES

What devbox_git does on Homelab

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

This tool executes git commands, which are external operations with side effects that depend on their arguments. While git operations are generally not destructive, they are Execute-class because they run external commands that modify system state.

From the tool's definition Tool description states it can "Run git status, pull, log, or clone" - these are operations that execute external commands (git commands) whose effects depend on arguments and can modify local state (pull, clone).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

devbox_git Rate-limited

devbox_git 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_git": {
      "limits": [
        {
          "counter": "devbox_git_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_git

What does the devbox_git tool do? +

Run git status, pull, log, or clone on the devbox. 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_git? +

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

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

Can I rate-limit devbox_git? +

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

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

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

// THE FULL RECORD

devbox_git is one line of Homelab's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →