repo-clone · Python MCP: Risk & Policy

WHAT IT DOES

What repo-clone does on Python

AI agents invoke repo-clone to trigger actions in Python. 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 repo-clone needs a policy

Cloning a repository triggers an external network operation that downloads and writes arbitrary code/content from GitHub to the local filesystem. This is an external operation with side effects beyond simple reads, and the content cloned depends on the arguments (repository URL). An AI agent misusing this tool could clone malicious repositories or exfiltrate/stage code, warranting high severity.

From the tool's definition Clones a GitHub repository

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Python, so you can run agents against it safely.

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 Python 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 Python 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 Python. 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 Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

repo-clone is one line of Python'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 →