restart_core

Restart Home Assistant Core. DANGEROUS — requires confirm=True.

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-core.md

WHAT IT DOES

What restart_core does on Ha Nexus Agent

AI agents invoke restart_core 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_core is rated High

Restarting Home Assistant Core is a significant operational action that disrupts all home automation services, disconnects devices, and interrupts active automations and integrations. While not destructive (data persists), it has system-wide effects that cannot be undone immediately and severely impacts availability.

From the tool's definition restart_core: 'Restart Home Assistant Core. DANGEROUS — requires confirm=True.' — explicitly restarts the entire home automation system.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

restart_core Rate-limited

restart_core 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_core": {
      "limits": [
        {
          "counter": "restart_core_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_core call is checked against it from then on.

FAQ

Questions about restart_core

What does the restart_core tool do? +

Restart Home Assistant Core. DANGEROUS — requires confirm=True. 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_core? +

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

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

Can I rate-limit restart_core? +

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

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

restart_core 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 →