git_rollback_file

Restore a single file to its state at a specific commit (default: last commit = undo changes).

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

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/fistacho-ha-nexus-agent/git-rollback-file.md

WHAT IT DOES

What git_rollback_file does on Ha Nexus Agent

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

RISK

Why git_rollback_file is rated Critical

Rolling back a file to a prior commit overwrites and irreversibly discards any changes made since that commit. The current state of the file is lost without a separate backup, making this a destructive operation. In a Home Assistant configuration context, this could overwrite critical config files, automations, or scripts with no easy recovery path.

From the tool's definition Restore a single file to its state at a specific commit (default: last commit = undo changes)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_rollback_file safely

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

git_rollback_file Hidden

git_rollback_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_rollback_file"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about git_rollback_file

What does the git_rollback_file tool do? +

Restore a single file to its state at a specific commit (default: last commit = undo changes). It is categorised as a Destructive tool in the Ha Nexus Agent 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_rollback_file? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for git_rollback_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 Ha Nexus Agent. Nothing to install.

What risk level is git_rollback_file? +

git_rollback_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_rollback_file? +

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

Set action: deny in the PolicyLayer policy for git_rollback_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_rollback_file? +

git_rollback_file is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent 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 →