# git_clone

Clone a repository to local filesystem

Agent View of the PolicyLayer registry record for `git_clone`. HTML page: https://policylayer.com/tools/git/git-clone

## Facts

- Tool: `git_clone`
- Server: Git (`@modelcontextprotocol/server-git`) — https://policylayer.com/tools/git.md
- Install: `npx -y @modelcontextprotocol/server-git`
- Homepage: https://github.com/modelcontextprotocol/server-git
- Risk category: Write (Medium risk)
- Registry record: grade D, identity verified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "git_clone",
    "arguments": {}
  }
}
```

## Why git_clone is rated Medium

Cloning writes new files to the local filesystem but is reversible (the cloned directory can be deleted). It does not delete or overwrite existing data, execute arbitrary code, or involve finances. The blast radius is medium since it could pull a large or malicious repository onto the local disk.

From the tool's own definition: "Clone a repository to local filesystem"

Risk signals: Downloads entire repository contents

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Git:

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

## Other tools on Git (13)

- `git_checkout` — Execute — https://policylayer.com/tools/git/git-checkout.md
- `git_branch` — Read — https://policylayer.com/tools/git/git-branch.md
- `git_diff` — Read — https://policylayer.com/tools/git/git-diff.md
- `git_diff_staged` — Read — https://policylayer.com/tools/git/git-diff-staged.md
- `git_diff_unstaged` — Read — https://policylayer.com/tools/git/git-diff-unstaged.md
- `git_log` — Read — https://policylayer.com/tools/git/git-log.md
- `git_show` — Read — https://policylayer.com/tools/git/git-show.md
- `git_status` — Read — https://policylayer.com/tools/git/git-status.md
- `git_add` — Write — https://policylayer.com/tools/git/git-add.md
- `git_commit` — Write — https://policylayer.com/tools/git/git-commit.md
- `git_create_branch` — Write — https://policylayer.com/tools/git/git-create-branch.md
- `git_init` — Write — https://policylayer.com/tools/git/git-init.md
- `git_reset` — Write — https://policylayer.com/tools/git/git-reset.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=git · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/git