Get quick statistics for git diff Use when native
AI agents call analyze_diff-stats to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries git diff statistics, which is a read-only operation that retrieves information about code changes without creating, modifying, executing, or deleting anything. It has no side effects and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'analyze_diff-stats' and description 'Get quick statistics for git diff' indicate retrieval and analysis of version control statistics without modification.
Attacks that exploit this kind of access
Get quick statistics for git diff Use when native. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for analyze_diff-stats: 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 Claude Flow. Nothing to install.
analyze_diff-stats 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 analyze_diff-stats 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 analyze_diff-stats. 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.
analyze_diff-stats is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.