Unstage files or reset HEAD. Use mode:file + path to restore a single file.
AI agents call git_reset to permanently remove resources in Context — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
git reset --hard and similar reset modes can permanently discard uncommitted changes and move HEAD to previous commits, destroying work that cannot be recovered without access to the reflog. While the description mentions 'unstage files' (reversible), the explicit mention of 'reset HEAD' and the tool's primary function of resetting commits makes this Destructive rather than Write.
From the tool's definition The tool description states 'reset HEAD' and 'restore a single file', which are git operations that can undo commits and discard changes. The name 'git_reset' combined with HEAD manipulation indicates irreversible modification of version control state.
Attacks that exploit this kind of access
Unstage files or reset HEAD. Use mode:file + path to restore a single file. It is categorised as a Destructive tool in the Context MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Context MCP server in PolicyLayer and add a rule for git_reset: 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 Context. Nothing to install.
git_reset 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 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. 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 is provided by the Context MCP server (vibhasdutta/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 →