turn_on

Turn on an entity. Optional: brightness (0-255), color_temp (mireds), rgb_color ([r,g,b]).

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

What turn_on does on Ha Nexus Agent

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

This tool sends a command to a physical smart home device to change its state to 'on', potentially adjusting brightness, color temperature, or RGB color. This constitutes executing an external operation with real-world side effects. While generally reversible (you can turn it off), the action itself is an execution of a command against a physical device.

From the tool's definition 'Turn on an entity. Optional: brightness (0-255), color_temp (mireds), rgb_color ([r,g,b])' — triggers an external operation (activating a physical smart home device/entity)

Questions about turn_on

What does the turn_on tool do? +

Turn on an entity. Optional: brightness (0-255), color_temp (mireds), rgb_color ([r,g,b]). 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_on? +

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

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

Can I rate-limit turn_on? +

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

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

turn_on 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.