get_git_diff
Get the full unified diff between two refs (default: HEAD~1..HEAD). Returns diff text, file list, and addition/deletion counts. Use to review changes before logging them to the ledger.
This record as markdown: /tools/2loch-ness6-mempalace-mcp-dev/get-git-diff.md
What get_git_diff does on Mcp Dev
AI agents call get_git_diff to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_git_diff is rated Low
This tool retrieves and displays git diff information between two references without making any changes to the codebase, files, or git state. It is purely informational and read-only, fitting the 'Read' category for retrieval/query operations with no side effects.
From the tool's definition Tool description states it "Get[s] the full unified diff" and "Returns diff text, file list, and addition/deletion counts." The phrase "Use to review changes before logging" indicates this is for inspection/querying purposes only.
Attacks that exploit this kind of access
The rule that runs get_git_diff safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_git_diff, this is the rule to start with:
get_git_diff is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every get_git_diff call is checked against it from then on.
Questions about get_git_diff
Get the full unified diff between two refs (default: HEAD~1..HEAD). Returns diff text, file list, and addition/deletion counts. Use to review changes before logging them to the ledger. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev 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 Mcp Dev. 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 Mcp Dev MCP server (2loch-ness6/mempalace-mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue