get_diff_stats
Get diff statistics (files changed, lines added/removed)
This record as markdown: /tools/agentics-ai-code-mcp/get-diff-stats.md
What get_diff_stats does on Code MCP Server
AI agents call get_diff_stats to retrieve information from Code MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_diff_stats is rated Low
This tool retrieves diff statistics—a form of data querying with no side effects. It computes and returns information about what changed (file count, line counts) without creating, modifying, deleting, executing, or moving resources. The read-only nature and lack of side effects place it firmly in the Read category with low severity, as misuse would only expose code change metadata, not cause harm.
From the tool's definition Tool name 'get_diff_stats' and description 'Get diff statistics (files changed, lines added/removed)' indicate a read-only query operation that retrieves and summarizes metadata about code changes without modifying data.
Attacks that exploit this kind of access
The rule that runs get_diff_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_diff_stats, this is the rule to start with:
get_diff_stats 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 Code MCP Server, apply this rule, and every get_diff_stats call is checked against it from then on.
Questions about get_diff_stats
Get diff statistics (files changed, lines added/removed). It is categorised as a Read tool in the Code MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for get_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 Code MCP Server. Nothing to install.
get_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 get_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 get_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.
get_diff_stats is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
This server
Across the catalogue