Get git diff between commits, branches, or working directory
AI agents call get_git_diff to retrieve information from Git PR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays differences between Git objects (commits, branches, working directory) without creating, modifying, deleting, or executing anything. It is purely informational and has no side effects on the repository state. This is a classic Read category operation.
From the tool's definition Tool name 'get_git_diff' and description 'Get git diff between commits, branches, or working directory' indicate a retrieval/query operation.
Attacks that exploit this kind of access
Get git diff between commits, branches, or working directory. It is categorised as a Read tool in the Git PR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git PR MCP Server MCP server in PolicyLayer and add a rule for get_git_diff: 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 PR MCP Server. Nothing to install.
get_git_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_git_diff 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.
Set action: deny in the PolicyLayer policy for get_git_diff. 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.
get_git_diff is provided by the Git PR MCP Server MCP server (peterj/git-pr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →