toggle_automation · Home Assistant MCP Server MCP

WHAT IT DOES

What toggle_automation does on Home Assistant MCP Server

AI agents invoke toggle_automation 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 toggle_automation needs a policy

Toggling an automation changes its active state, which can trigger or suppress smart home actions (lights, locks, alarms, etc.). This is an external operation with real-world effects, making it Execute. Misuse could enable/disable security or safety automations, hence medium severity.

From the tool's definition 'Active ou désactive une automatisation Home Assistant' — toggles (activates or deactivates) a Home Assistant automation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

toggle_automation Rate-limited

toggle_automation 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": {
    "toggle_automation": {
      "limits": [
        {
          "counter": "toggle_automation_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 toggle_automation

What does the toggle_automation tool do? +

Active ou désactive une automatisation Home Assistant. 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 toggle_automation? +

Register the Home Assistant MCP Server MCP server in PolicyLayer and add a rule for toggle_automation: 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 toggle_automation? +

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

Can I rate-limit toggle_automation? +

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

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

toggle_automation is provided by the Home Assistant MCP Server MCP server (jonathan97480/mcphomeassistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.