delete_zone

Delete a zone via WS config/zone/delete (accepts zone helper id or zone.<id>).

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/delete-zone.md

WHAT IT DOES

What delete_zone does on Ha Nexus Agent

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

This tool irreversibly deletes zone data from Home Assistant, a destructive action that cannot be undone without manual reconfiguration. While not life-safety critical, zones are configuration entities used for presence detection and location-based automation; deletion could disrupt location-aware routines and presence detection logic.

From the tool's definition Tool name is 'delete_zone' and description states 'Delete a zone' — explicit use of the delete operation. The tool permanently removes a zone helper configuration via the Home Assistant WebSocket API endpoint `config/zone/delete`.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_zone Hidden

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

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

FAQ

Questions about delete_zone

What does the delete_zone tool do? +

Delete a zone via WS config/zone/delete (accepts zone helper id or zone.<id>). 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 delete_zone? +

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

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

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

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

delete_zone 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

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →