git_show

Show the contents of a commit

SERVERGit SOURCE@modelcontextprotocol/server-git

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/git/git-show.md

WHAT IT DOES

What git_show does on Git

AI agents call git_show 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.

RISK

Why git_show is rated Low

The git_show command retrieves historical commit information (files, diffs, metadata) from a repository. It is inherently a read operation with no side effects—it cannot create, modify, delete, or execute code. The blast radius is minimal since misuse would only expose existing commit data already in the repository.

From the tool's definition Tool name 'git_show' and description 'Show the contents of a commit' indicate a read-only operation that retrieves and displays commit data without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_show safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_show, this is the rule to start with:

git_show Allowed

git_show is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_show": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every git_show call is checked against it from then on.

FAQ

Questions about git_show

What does the git_show tool do? +

Show the contents of a commit. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_show? +

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

What risk level is git_show? +

git_show is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_show? +

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

Set action: deny in the PolicyLayer policy for git_show. 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_show? +

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

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 14 Git tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →