stop_ha

Stop Home Assistant. WARNING: requires manual restart.

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/stop-ha.md

WHAT IT DOES

What stop_ha does on Ha Nexus Agent

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

Stopping Home Assistant halts all smart home automation, device control, and monitoring. Because recovery requires a manual restart, this action cannot be undone automatically. It is effectively an irreversible disruption with a very high blast radius — all connected devices, automations, and integrations go offline until someone physically intervenes.

From the tool's definition 'Stop Home Assistant. WARNING: requires manual restart.' — stopping the HA server is irreversible without physical/manual intervention and takes down the entire smart home platform.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stop_ha Hidden

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

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

FAQ

Questions about stop_ha

What does the stop_ha tool do? +

Stop Home Assistant. WARNING: requires manual restart. 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 stop_ha? +

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

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

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

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

stop_ha 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

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →