Reset the current branch to a specific commit. This changes where the branch HEAD points to, with different modes affecting the working directory and index differently (hard: discard all changes, soft: keep staged changes, mixed: unstage but keep changes). IMPORTANT: Always use a full, absolute p...
AI agents call git_reset_commit to permanently remove resources in Git MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
git_reset_commit can irreversibly discard uncommitted changes in the working directory when used with hard mode. While soft and mixed modes are reversible (categorizing as Write), the presence of hard mode that cannot be undone places this tool in the Destructive category per the severity hierarchy. An AI agent misusing this with hard mode could permanently lose user work.
From the tool's definition Tool description states it 'Reset the current branch to a specific commit' with 'hard: discard all changes' mode, which irreversibly loses uncommitted work. The 'mixed' and 'soft' modes are reversible, but the hard mode capability makes this destructive.
Attacks that exploit this kind of access
Reset the current branch to a specific commit. This changes where the branch HEAD points to, with different modes affecting the working directory and index differently (hard: discard all changes, soft: keep staged changes, mixed: unstage but keep changes). IMPORTANT: Always use a full, absolute path to the repository to ensure proper functionality. It is categorised as a Destructive tool in the Git MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for git_reset_commit: 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 MCP Server. Nothing to install.
git_reset_commit 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_reset_commit 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_reset_commit. 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_reset_commit is provided by the Git MCP Server MCP server (wty0512/git-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 →