exec

Executes arbitrary commands inside a running Docker container and returns structured output. WARNING: may execute untrusted code.

SERVERGit SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-git/exec.md

WHAT IT DOES

What exec does on Git

AI agents invoke exec to trigger actions in Git. 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.

RISK

Why exec is rated High

This tool allows execution of arbitrary commands within a Docker container, which is a classic Execute risk. The explicit warning about untrusted code and the lack of built-in restrictions on command arguments means an AI agent could run any command with unpredictable side effects (data exfiltration, system compromise, lateral movement, etc.).

From the tool's definition Tool description explicitly states 'Executes arbitrary commands inside a running Docker container' and includes 'WARNING: may execute untrusted code.' The word 'arbitrary' indicates unrestricted command execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs exec safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For exec, this is the rule to start with:

exec Rate-limited

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": {
    "exec": {
      "limits": [
        {
          "counter": "exec_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every exec call is checked against it from then on.

FAQ

Questions about exec

What does the exec tool do? +

Executes arbitrary commands inside a running Docker container and returns structured output. WARNING: may execute untrusted code. It is categorised as a Execute tool in the Git MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on exec? +

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

What risk level is exec? +

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

Can I rate-limit exec? +

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

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

exec is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →