restart_ha

Restart Home Assistant. WARNING: causes ~30s downtime.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/restart-ha.md

WHAT IT DOES

What restart_ha does on Ha Nexus Agent

AI agents invoke restart_ha to trigger actions in Ha Nexus Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why restart_ha is rated High

This tool triggers an external operation (restart of the Home Assistant service) whose effects depend on when it is invoked. While not destructive (data persists) or financial, it is an Execute category risk because it runs a control operation that causes service downtime and disruption to a home automation system.

From the tool's definition Tool name 'restart_ha' and description 'Restart Home Assistant. WARNING: causes ~30s downtime' indicate execution of a system restart operation with acknowledged side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

restart_ha Rate-limited

restart_ha stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restart_ha": {
      "limits": [
        {
          "counter": "restart_ha_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about restart_ha

What does the restart_ha tool do? +

Restart Home Assistant. WARNING: causes ~30s downtime. It is categorised as a Execute tool in the Ha Nexus Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on restart_ha? +

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

restart_ha is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit restart_ha? +

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

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

restart_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 → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →