git_restore_file

Discard changes to a file (git restore).

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-restore-file.md

WHAT IT DOES

What git_restore_file does on LocalAnt

AI agents call git_restore_file 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_restore_file is rated Critical

git restore discards uncommitted changes to a file, which is irreversible — those changes cannot be recovered once discarded. This is a destructive operation with potentially high blast radius if an AI agent accidentally discards meaningful work in progress.

From the tool's definition Discard changes to a file (git restore)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_restore_file 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_restore_file, this is the rule to start with:

git_restore_file Hidden

git_restore_file 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_restore_file"
  ]
}

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_restore_file call is checked against it from then on.

FAQ

Questions about git_restore_file

What does the git_restore_file tool do? +

Discard changes to a file (git restore). 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_restore_file? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for git_restore_file: 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_restore_file? +

git_restore_file 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_restore_file? +

Yes. Add a rate_limit block to the git_restore_file 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_restore_file completely? +

Set action: deny in the PolicyLayer policy for git_restore_file. 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_restore_file? +

git_restore_file 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

delete_file on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →