# git_status

Show the working tree status

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

## Facts

- Tool: `git_status`
- 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: Read (Low risk)
- Registry record: grade D, identity verified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why git_status is rated Low

git_status is a Git query command that displays the current state of the working directory and staging area. It has no side effects, performs no modifications, and merely retrieves and displays status information. This is a low-severity read operation with minimal risk even if misused by an agent.

From the tool's own definition: "Tool name 'git_status' and description 'Show the working tree status' indicate a read-only query operation that retrieves repository status information without modifying anything."

## Use case

AI agents call git_status to retrieve information from Git without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_status": {}
  }
}
```

## 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_add` — Write — https://policylayer.com/tools/git/git-add.md
- `git_clone` — Write — https://policylayer.com/tools/git/git-clone.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