get_diff_stats

Get diff statistics (files changed, lines added/removed)

SERVERCode MCP Server SOURCEagentics-ai/code-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_diff_stats

What does the get_diff_stats tool do? +

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.

How do I enforce a policy on get_diff_stats? +

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.

What risk level is get_diff_stats? +

get_diff_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_diff_stats? +

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.

How do I block get_diff_stats completely? +

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.

What MCP server provides get_diff_stats? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Code MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.