restore_backup

Restore a full backup by slug. DANGEROUS — requires confirm=True.

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/restore-backup.md

WHAT IT DOES

What restore_backup does on Ha Nexus Agent

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

Restoring a backup is a destructive, irreversible operation that replaces the entire Home Assistant system state. Any configuration, automations, or data created after the backup point would be permanently lost. The description itself flags this as DANGEROUS and requires an explicit confirmation flag, indicating the authors recognize the high risk.

From the tool's definition 'Restore a full backup by slug. DANGEROUS — requires confirm=True.' — restoring a full backup overwrites the current system state irreversibly, destroying all configuration and data changes made after the backup was taken.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

restore_backup Hidden

restore_backup 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": [
    "restore_backup"
  ]
}

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

FAQ

Questions about restore_backup

What does the restore_backup tool do? +

Restore a full backup by slug. DANGEROUS — requires confirm=True. 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 restore_backup? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for restore_backup: 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 restore_backup? +

restore_backup 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 restore_backup? +

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

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

restore_backup 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

create_full_backup on Android Forensics ADB MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →