Classify git diff change type Use when native
AI agents call analyze_diff-classify 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 examines git diff output to classify change types, which is a read-only analytical operation. It retrieves and categorizes information about code changes without altering repositories, executing commands, or triggering side effects.
From the tool's definition Tool name 'analyze_diff-classify' and description 'Classify git diff change type' indicate it analyzes and categorizes existing diffs without modifying code or git state. No write, execute, or destructive operations are implied.
Attacks that exploit this kind of access
Classify git diff change type 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-classify: 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-classify 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-classify 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-classify. 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-classify 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.