Show differences in files (unstaged or staged changes)
AI agents call git_diff to retrieve information from MCP File & Git Manager Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_diff is a query/inspection tool that compares file versions and returns textual differences. It has no side effects: it neither modifies files, executes code, deletes data, nor commits changes. The blast radius of misuse is minimal—an attacker can only view diffs of local repository state, gaining information disclosure at most. This is characteristic of Read category tools.
From the tool's definition Tool description states 'Show differences in files (unstaged or staged changes)' — a read-only operation that retrieves and displays diff output without modifying or executing code.
Attacks that exploit this kind of access
Show differences in files (unstaged or staged changes). It is categorised as a Read tool in the MCP File & Git Manager Server MCP Server, which means it retrieves data without modifying state.
Register the MCP File & Git Manager Server MCP server in PolicyLayer and add a rule for 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 MCP File & Git Manager Server. Nothing to install.
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 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 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.
git_diff is provided by the MCP File & Git Manager Server MCP server (osamaloup/mcp-file-git-server). 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 →