AI agents call git_diff to retrieve information from LuzzyTool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_diff retrieves and displays information about changes between Git commits or the working directory—a read-only operation with no side effects. It does not modify, delete, execute code, or perform financial transactions. The highest risk is if an AI agent uses this to discover sensitive information in diffs, but the tool itself is fundamentally a query operation.
From the tool's definition Tool description explicitly labels this as '【查询操作】' (query operation) and the functionality is 'view Git differences' (查看 Git 差异). Parameters like staged=true and stat=true control what difference information is displayed, but no modifications occur.
Attacks that exploit this kind of access
【查询操作】查看 Git 差异。staged=true 显示暂存区差异，stat=true 只显示文件级统计。. It is categorised as a Read tool in the LuzzyTool MCP Server, which means it retrieves data without modifying state.
Register the LuzzyTool 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 LuzzyTool. 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 LuzzyTool MCP server (luzzymeow/luzzytool). 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 →