# git_diff_unstaged

Show unstaged changes in working directory

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

## Facts

- Tool: `git_diff_unstaged`
- 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_diff_unstaged",
    "arguments": {}
  }
}
```

## Why git_diff_unstaged is rated Low

The tool retrieves and displays information about uncommitted changes in the working directory without creating, modifying, or deleting any data. This is a non-destructive, side-effect-free inspection operation characteristic of Read-category tools.

From the tool's own definition: "Tool name and description indicate it 'Show[s] unstaged changes' — a read-only query of the working directory state with no modifications to files or repository."

## Use case

AI agents call git_diff_unstaged 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_diff_unstaged": {}
  }
}
```

## 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_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_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