reload_scenes

Reload scenes from YAML.

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/reload-scenes.md

WHAT IT DOES

What reload_scenes does on Ha Nexus Agent

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

This tool triggers an external operation — reloading scene configurations from YAML files in Home Assistant. It doesn't merely read data, nor does it irreversibly delete anything, but it executes a system action that applies configuration changes and can affect smart home device states/behavior. Misuse could disrupt active scene configurations.

From the tool's definition Reload scenes from YAML

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reload_scenes Rate-limited

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

FAQ

Questions about reload_scenes

What does the reload_scenes tool do? +

Reload scenes from YAML. 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 reload_scenes? +

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

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

Can I rate-limit reload_scenes? +

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

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

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