Shows every author who has ever committed to a file, ranked by number of commits. Includes current line ownership, commit percentage, and the date range they were active on the file.
AI agents call file_contributors to retrieve information from Git Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries git repository metadata (author information, commit counts, ownership statistics, and activity dates) without any side effects. It is a read-only analysis tool that gathers historical information about file contributors.
From the tool's definition Tool description states it 'Shows every author who has ever committed to a file' and 'Includes current line ownership, commit percentage, and the date range they were active.' These are purely informational queries about git history with no modification,…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Shows every author who has ever committed to a file, ranked by number of commits. Includes current line ownership, commit percentage, and the date range they were active on the file. It is categorised as a Read tool in the Git Context MCP Server, which means it retrieves data without modifying state.
Register the Git Context MCP server in PolicyLayer and add a rule for file_contributors: 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 Context. Nothing to install.
file_contributors 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 file_contributors 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 file_contributors. 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.
file_contributors is provided by the Git Context MCP server (muhannad-hash/git-context-mcp). 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 →