# git_checkout

A execute tool on the GitHub MCP server.

Agent View of the PolicyLayer registry record for `git_checkout`. HTML page: https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-checkout

## Facts

- Tool: `git_checkout`
- Server: GitHub (`oci:ghcr.io/aifity/omnigit-mcp:0.5.0`) — https://policylayer.com/tools/io-github-aifity-omnigit-mcp.md
- Homepage: https://github.com/aifity/omnigit-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- 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_checkout",
    "arguments": {}
  }
}
```

## Why git_checkout is rated High

Git checkout switches branches or restores working tree files, which is an operation that triggers external git operations and can alter repository state. The description is minimal/uninformative, but the tool name clearly references a git operation that changes the working tree or branch context. This could affect code being built/deployed, making it high severity if misused by an AI agent.

From the tool's own definition: "Tool name 'git_checkout' and description 'Git checkout'"

## Use case

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

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_checkout": {
      "limits": [
        {
          "counter": "git_checkout_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on GitHub (244)

- `delete_file` — Destructive — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/delete-file.md
- `force` — Destructive — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/force.md
- `git_reset` — Destructive — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-reset.md
- `git_worktree_prune` — Destructive — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-worktree-prune.md
- `git_worktree_remove` — Destructive — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-worktree-remove.md
- `actions_run_trigger` — Execute — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/actions-run-trigger.md
- `detach` — Execute — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/detach.md
- `git_pull` — Execute — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-pull.md
- `git_push` — Execute — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-push.md
- `git_worktree_add` — Execute — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-worktree-add.md
- `git_worktree_lock` — Execute — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/git-worktree-lock.md
- `autoInit` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/autoinit.md
- `base` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/base.md
- `base_branch` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/base-branch.md
- `base_ref` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/base-ref.md
- `before_id` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/before-id.md
- `branch` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/branch.md
- `branch_name` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/branch-name.md
- `color` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/color.md
- `comment_id` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/comment-id.md
- `commentId` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/commentid.md
- `commit_title` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/commit-title.md
- `commitID` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/commitid.md
- `direction` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/direction.md
- `gist_id` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/gist-id.md
- `issue_number` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/issue-number.md
- `item_type` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/item-type.md
- `job_id` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/job-id.md
- `message` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/message.md
- `new_name` — Other — https://policylayer.com/tools/io-github-aifity-omnigit-mcp/new-name.md
- …and 214 more: https://policylayer.com/tools/io-github-aifity-omnigit-mcp.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=io-github-aifity-omnigit-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-aifity-omnigit-mcp