turn_on

Turn on an entity through homeassistant.turn_on.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

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/mcp-control-plane/turn-on.md

WHAT IT DOES

What turn_on does on Mcp Control Plane

AI agents invoke turn_on to trigger actions in Mcp Control Plane. 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_on is rated High

This tool triggers an external operation in Home Assistant, changing the state of a physical or virtual entity (e.g., lights, switches, appliances). It causes real-world side effects by activating devices, making it an Execute action. Severity is medium because misuse could activate unintended devices (e.g., unlocking doors, turning on heating), but it is generally reversible via a corresponding turn_off action.

From the tool's definition Turn on an entity through homeassistant.turn_on

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs turn_on safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For turn_on, this is the rule to start with:

turn_on Rate-limited

turn_on 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_on": {
      "limits": [
        {
          "counter": "turn_on_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 Mcp Control Plane, apply this rule, and every turn_on call is checked against it from then on.

FAQ

Questions about turn_on

What does the turn_on tool do? +

Turn on an entity through homeassistant.turn_on. It is categorised as a Execute tool in the Mcp Control Plane 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 Mcp Control Plane 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 Mcp Control Plane. 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 Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane 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 →