git_reset_hard

git reset --hard (DESTRUCTIVE: discards commits and working-tree changes).

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/git-reset-hard.md

WHAT IT DOES

What git_reset_hard does on LocalAnt

AI agents call git_reset_hard to permanently remove resources in LocalAnt, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why git_reset_hard is rated Critical

git reset --hard is an irreversible operation that destroys both staged and unstaged changes in the working tree and can rewrite commit history. Once executed, affected changes cannot be recovered without access to git reflog or backups.

From the tool's definition Tool name explicitly states 'git_reset_hard'; description explicitly states '(DESTRUCTIVE: discards commits and working-tree changes)'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_reset_hard safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_reset_hard, this is the rule to start with:

git_reset_hard Hidden

git_reset_hard is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "git_reset_hard"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every git_reset_hard call is checked against it from then on.

FAQ

Questions about git_reset_hard

What does the git_reset_hard tool do? +

git reset --hard (DESTRUCTIVE: discards commits and working-tree changes). It is categorised as a Destructive tool in the LocalAnt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on git_reset_hard? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for git_reset_hard: 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 LocalAnt. Nothing to install.

What risk level is git_reset_hard? +

git_reset_hard is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit git_reset_hard? +

Yes. Add a rate_limit block to the git_reset_hard 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.

How do I block git_reset_hard completely? +

Set action: deny in the PolicyLayer policy for git_reset_hard. 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.

What MCP server provides git_reset_hard? +

git_reset_hard is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →delete_git_repo on cPanel MCP Server →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →