Commit-area tool. Use action=add|restore|commit|reset|revert|undo|nuke|wip|unstage|amend.
AI agents call git_commits to permanently remove resources in Git — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While this tool includes reversible operations like 'add', 'commit', and 'amend', it also explicitly includes 'nuke' and 'revert' which are destructive actions capable of permanently discarding work. Once a commit is nuked or reverted and pushed to a shared repository, recovery becomes significantly harder. The presence of any irreversible action elevates this to Destructive category per the severity hierarchy.
From the tool's definition Tool description includes actions 'revert', 'reset', 'nuke', and 'undo' which can irreversibly alter or discard commits and changes. The 'nuke' action in particular suggests permanent deletion of data.
Attacks that exploit this kind of access
Commit-area tool. Use action=add|restore|commit|reset|revert|undo|nuke|wip|unstage|amend. It is categorised as a Destructive tool in the Git MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git MCP server in PolicyLayer and add a rule for git_commits: 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. Nothing to install.
git_commits is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the git_commits 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 git_commits. 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.
git_commits is provided by the Git MCP server (selfagency/git-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 →