start_multiple_zones · Home Controller MCP: Risk & Policy

WHAT IT DOES

What start_multiple_zones does on Home Controller

AI agents invoke start_multiple_zones to trigger actions in Home Controller. 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 start_multiple_zones needs a policy

This tool executes commands to activate physical devices (likely sauna zones based on HUUM being a sauna manufacturer). While not destructive, it performs irreversible state changes to real-world systems. The severity is high because misuse could cause energy waste, discomfort, equipment strain, or safety hazards (e.g., starting a sauna unintentionally).

From the tool's definition Tool name 'start_multiple_zones' and description 'Queue multiple zones to run sequentially' indicates the tool triggers external operations (starting sauna zones or HVAC zones) whose effects depend on zone_id and duration arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_multiple_zones Rate-limited

start_multiple_zones 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": {
    "start_multiple_zones": {
      "limits": [
        {
          "counter": "start_multiple_zones_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 Controller, so you can run agents against it safely.

FAQ

Questions about start_multiple_zones

What does the start_multiple_zones tool do? +

Queue multiple zones to run sequentially. Each item is { zone_id, minutes, sortOrder }. It is categorised as a Execute tool in the Home Controller MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_multiple_zones? +

Register the Home Controller MCP server in PolicyLayer and add a rule for start_multiple_zones: 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 Controller. Nothing to install.

What risk level is start_multiple_zones? +

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

Can I rate-limit start_multiple_zones? +

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

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

start_multiple_zones is provided by the Home Controller MCP server (winsthuang/home-controller). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.