git_rollback_file
Restore a single file to its state at a specific commit (default: HEAD = undo uncommitted changes).
This record as markdown: /tools/fistacho-ha-nexus-agent/git-rollback-file.md
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.
Why git_rollback_file is rated Critical
Rolling back a file overwrites its current contents with a previous version, irreversibly discarding any uncommitted or post-commit changes to that file. This is a destructive operation since the overwritten state cannot be recovered without external backups. In a Home Assistant configuration context, this could revert critical config files, automations, or scripts without warning.
From the tool's definition Restore a single file to its state at a specific commit (default: HEAD = undo uncommitted changes)
Attacks that exploit this kind of access
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 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
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.
Questions about git_rollback_file
Restore a single file to its state at a specific commit (default: HEAD = undo uncommitted 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.
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.
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.
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.
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.
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.
More on Ha Nexus Agent, and thousands of servers like it.
Across the catalogue