turn_off

Turn off an entity.

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/turn-off.md

WHAT IT DOES

What turn_off does on Ha Nexus Agent

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

This tool sends a command to Home Assistant to change the state of a physical or virtual entity to 'off'. It is an action with real-world effects (e.g., turning off lights, locks, switches, or HVAC systems). It is not purely destructive/irreversible, but it executes an external operation with potentially significant consequences (e.g., turning off a security system or heating). Execute is the appropriate category.

From the tool's definition 'Turn off an entity' — triggers an external operation (state change) on a smart home device

Attacks that exploit this kind of access

RECOMMENDED RULE

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

turn_off Rate-limited

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

FAQ

Questions about turn_off

What does the turn_off tool do? +

Turn off an entity. 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 turn_off? +

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

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

Can I rate-limit turn_off? +

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

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

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