git_clone · Git MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_clone does on Git MCP Server

AI agents use git_clone to create or update resources in Git MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git MCP Server environment.

WHY IT NEEDS A POLICY

Why git_clone needs a policy

git_clone creates new files and directories on the local filesystem by downloading a remote repository. This is a Write operation — it creates data locally but does not delete or overwrite existing data, execute code, or involve finances. Misuse could result in downloading large or malicious repositories, hence medium severity.

From the tool's definition Clone a Git repository. Downloads a repository from a remote location and creates a local copy with all its history.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_clone Rate-limited

git_clone stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_clone": {
      "limits": [
        {
          "counter": "git_clone_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about git_clone

What does the git_clone tool do? +

Clone a Git repository. Downloads a repository from a remote location and creates a local copy with all its history. Supports specifying branches, creating shallow clones, and more. It is categorised as a Write tool in the Git MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_clone? +

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

What risk level is git_clone? +

git_clone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit git_clone? +

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

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

git_clone is provided by the Git MCP Server MCP server (wty0512/git-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.