reload_all
Reload core configuration (automations, scripts, scenes, groups, etc.).
This record as markdown: /tools/fistacho-ha-nexus-agent/reload-all.md
What reload_all does on Ha Nexus Agent
AI agents invoke reload_all 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.
Why reload_all is rated High
This tool triggers a system-wide reload of Home Assistant's core configuration including automations, scripts, and scenes. It executes an operational action that restarts/reloads active components, potentially disrupting running automations and smart home state. It is not simply reading data, nor is it irreversibly destructive, but it executes a broad system-level operation with significant blast radius if misused.
From the tool's definition Reload core configuration (automations, scripts, scenes, groups, etc.)
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reload_all 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 reload_all, this is the rule to start with:
reload_all 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every reload_all call is checked against it from then on.
Questions about reload_all
Reload core configuration (automations, scripts, scenes, groups, etc.). 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.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for reload_all: 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.
reload_all 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 reload_all 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 reload_all. 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.
reload_all 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.
More on Ha Nexus Agent, and thousands of servers like it.
Across the catalogue