get_git_churn

Per-file git churn: commits, unique authors, frequency, volatility assessment. Requires git. Use to identify frequently-changed files. For combined churn+complexity hotspots use get_risk_hotspots instead. Read-only. Returns JSON: { results: [{ file, commits, authors, frequency, volatility }], tot...

SERVERTrace SOURCEnikolai-vysotskyi/trace-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/nikolai-vysotskyi-trace-mcp/get-git-churn.md

WHAT IT DOES

What get_git_churn does on Trace

AI agents call get_git_churn to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_git_churn is rated Low

This tool only retrieves and queries git history metadata to analyze code churn patterns. It performs no modifications, deletions, or side effects. The explicit 'Read-only' designation confirms it is a pure data retrieval operation. Severity is low as misuse would only expose git statistics, not cause system damage or financial impact.

From the tool's definition Tool description states: 'Per-file git churn: commits, unique authors, frequency, volatility assessment' and explicitly marks 'Read-only.' Returns JSON with metrics (commits, authors, frequency, volatility) without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_git_churn safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_git_churn, this is the rule to start with:

get_git_churn Allowed

get_git_churn is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_git_churn": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_git_churn call is checked against it from then on.

FAQ

Questions about get_git_churn

What does the get_git_churn tool do? +

How do I enforce a policy on get_git_churn? +

Register the Trace MCP server in PolicyLayer and add a rule for get_git_churn: 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 Trace. Nothing to install.

What risk level is get_git_churn? +

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

Can I rate-limit get_git_churn? +

Yes. Add a rate_limit block to the get_git_churn 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_git_churn completely? +

Set action: deny in the PolicyLayer policy for get_git_churn. 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_git_churn? +

get_git_churn is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

aiva_get_churn_risk on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →