repo-clone

Clones a GitHub repository. Returns structured data with success status, repo name, target directory, and message.

SERVERDocker SOURCE@paretools/docker

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-docker/repo-clone.md

WHAT IT DOES

What repo-clone does on Docker

AI agents invoke repo-clone to trigger actions in Docker. 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 repo-clone is rated High

Cloning a repository executes an external git operation that pulls remote code onto the local filesystem. It triggers an external operation (network fetch + filesystem write) whose effects depend on the arguments (which repo, which directory). This goes beyond a simple read/query as it modifies the local environment by creating files and directories, placing it in the Execute category.

From the tool's definition Clones a GitHub repository... target directory

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs repo-clone safely

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

repo-clone Rate-limited

repo-clone 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": {
    "repo-clone": {
      "limits": [
        {
          "counter": "repo-clone_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 Docker, apply this rule, and every repo-clone call is checked against it from then on.

FAQ

Questions about repo-clone

What does the repo-clone tool do? +

Clones a GitHub repository. Returns structured data with success status, repo name, target directory, and message. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on repo-clone? +

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

What risk level is repo-clone? +

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

Can I rate-limit repo-clone? +

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

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

repo-clone is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

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

Across the catalogue

deploy_git_repo on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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