Restart Home Assistant ⚠️ WARNING: Temporarily disrupts all Home Assistant operations Returns: Result of restart operation
AI agents invoke restart_ha to trigger actions in Hass-MCP. 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.
This tool executes a restart of the Home Assistant system itself, which is an irreversible operation in the sense that it will interrupt all running automations, queries, and smart home controls until the restart completes. While technically recoverable (the system comes back online), the action itself is an Execute-category operation that triggers external system behavior.
From the tool's definition Tool name 'restart_ha' and description 'Restart Home Assistant' indicate execution of a system-level restart command.
Documented attack patterns abuse exactly the kind of access restart_ha gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hass-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for restart_ha:
{
"version": "1",
"default": "deny",
"tools": {
"restart_ha": {
"limits": [
{
"counter": "restart_ha_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Restart Home Assistant ⚠️ WARNING: Temporarily disrupts all Home Assistant operations Returns: Result of restart operation. It is categorised as a Execute tool in the Hass-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hass- 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 Hass-MCP. Nothing to install.
restart_ha is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
restart_ha is provided by the Hass- MCP server (voska/hass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Hass-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Hass-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.