Shows changes in working directory not yet staged
AI agents call git_diff_unstaged to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs read-only inspection of the working directory state. It retrieves diff information between the working directory and staged changes, which is a standard query operation with no side effects, reversible operations, code execution, data deletion, or financial impact. This is a safe diagnostic tool.
From the tool's definition Tool name 'git_diff_unstaged' and description 'Shows changes in working directory not yet staged' indicate a query/inspection operation that retrieves and displays diff information without modifying any data.
Attacks that exploit this kind of access
Shows changes in working directory not yet staged. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git_diff_unstaged: 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 GitHub MCP Server. Nothing to install.
git_diff_unstaged 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_unstaged 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_unstaged. 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_unstaged is provided by the GitHub MCP Server MCP server (lyderdev/github-mcp-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 →