Get files with most changes (churn)
AI agents call get_file_churn to retrieve information from Git Metrics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries git repository statistics to identify files with high change frequency (churn). It retrieves and analyzes existing data from the repository without creating, modifying, deleting, or executing any operations. This is a purely informational/analytical Read operation. Low severity because misuse would only expose repository analysis metrics, not compromise data integrity or enable destructive actions.
From the tool's definition Tool name 'get_file_churn' and description 'Get files with most changes (churn)' indicate data retrieval/querying of git repository metrics. The verb 'Get' and the read-only nature of analyzing historical commit data show no side effects or modifications.
Attacks that exploit this kind of access
Get files with most changes (churn). It is categorised as a Read tool in the Git Metrics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git Metrics MCP Server MCP server in PolicyLayer and add a rule for get_file_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 Git Metrics MCP Server. Nothing to install.
get_file_churn 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_file_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.
Set action: deny in the PolicyLayer policy for get_file_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.
get_file_churn is provided by the Git Metrics MCP Server MCP server (jonmatum/git-metrics-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →