tools-lights-control · Home Assistant MCP Server MCP

WHAT IT DOES

What tools-lights-control does on Home Assistant MCP Server

AI agents invoke tools-lights-control to trigger actions in Home Assistant MCP Server. 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 IT NEEDS A POLICY

Why tools-lights-control needs a policy

This tool executes commands against physical smart home devices (lights), causing real-world state changes such as turning lights on/off and adjusting settings. While reversible in principle, it directly controls physical infrastructure, making misuse potentially disruptive (e.g., turning off lights in critical areas).

From the tool's definition 'Control Home Assistant lights including turning on/off, brightness, color, effects, etc.' — triggers external real-world operations on smart home lighting devices

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tools-lights-control Rate-limited

tools-lights-control 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": {
    "tools-lights-control": {
      "limits": [
        {
          "counter": "tools-lights-control_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Home Assistant MCP Server, so you can run agents against it safely.

FAQ

Questions about tools-lights-control

What does the tools-lights-control tool do? +

Control Home Assistant lights including turning on/off, brightness, color, effects, etc. It is categorised as a Execute tool in the Home Assistant MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tools-lights-control? +

Register the Home Assistant MCP Server MCP server in PolicyLayer and add a rule for tools-lights-control: 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 Home Assistant MCP Server. Nothing to install.

What risk level is tools-lights-control? +

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

Can I rate-limit tools-lights-control? +

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

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

tools-lights-control is provided by the Home Assistant MCP Server MCP server (oleander/home-assistant-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.