Quick risk assessment for git diff Use when native
AI agents call analyze_diff-risk 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.
This tool reads and evaluates a git diff to assess risk, which is a query/analysis operation with no side effects. It retrieves information about code changes and produces a risk score or report, but does not execute code, modify data, delete anything, or move money. The low severity reflects minimal blast radius—misuse would only produce incorrect risk assessments, not harm systems or data.
From the tool's definition Tool name 'analyze_diff-risk' and description 'Quick risk assessment for git diff' indicate analysis and assessment of existing data (a git diff), with no modification, execution, or deletion. The term 'analyze' and 'assessment' are passive operations.
Attacks that exploit this kind of access
Quick risk assessment 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-risk: 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-risk 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-risk 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-risk. 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-risk 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.