disable_automation · Home Assistant MCP Server MCP

WHAT IT DOES

What disable_automation does on Home Assistant MCP Server

AI agents use disable_automation to create or update resources in Home Assistant MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Home Assistant MCP Server environment.

WHY IT NEEDS A POLICY

Why disable_automation needs a policy

Disabling an automation modifies its configuration state but does not destroy data or irreversibly delete it—the automation remains in the system and can be re-enabled. This places it in the Write category rather than Destructive.

From the tool's definition Tool name 'disable_automation' and description 'Disable an automation' indicate modification of automation state. This is a reversible state change operation on Home Assistant automations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_automation Rate-limited

disable_automation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disable_automation": {
      "limits": [
        {
          "counter": "disable_automation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 disable_automation

What does the disable_automation tool do? +

Disable an automation. It is categorised as a Write tool in the Home Assistant MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disable_automation? +

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

disable_automation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disable_automation? +

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

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

disable_automation is provided by the Home Assistant MCP Server MCP server (mjrestivo16/mcp-homeassistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.