Get git diff (changes in working directory or staged changes)
AI agents call get_diff to retrieve information from Git Helper MCP 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 git diff output, showing what has changed in the working directory or staged area. It has no side effects—it does not modify, delete, or execute anything. It is purely informational, consistent with the Read category (search, list, get, fetch). The broader server context confirms this is a query-focused tool for exploring repository state through natural language.
From the tool's definition Tool name 'get_diff' and description 'Get git diff (changes in working directory or staged changes)' indicate retrieval of diff information. The verb 'Get' and the read-only nature of examining changes without applying them clarifies this is a query operation.
Attacks that exploit this kind of access
Get git diff (changes in working directory or staged changes). It is categorised as a Read tool in the Git Helper MCP MCP Server, which means it retrieves data without modifying state.
Register the Git Helper MCP server in PolicyLayer and add a rule for get_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 Helper MCP. Nothing to install.
get_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_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_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_diff is provided by the Git Helper MCP server (letscodethebrain/git-helper-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 →