intent_handle · Homeassistant MCP: Risk & Policy

WHAT IT DOES

What intent_handle does on Homeassistant

AI agents invoke intent_handle to trigger actions in Homeassistant. 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 intent_handle needs a policy

In Home Assistant, intent handling processes natural language intents and triggers actions on devices and services. Given the server's purpose of controlling Home Assistant devices and the sibling tools (call_service, automation_control, alarm_control, etc.), intent_handle likely executes commands or triggers automations.

From the tool's definition Tool name 'intent_handle' on a Home Assistant MCP server that controls devices and services; description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

intent_handle Rate-limited

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

FAQ

Questions about intent_handle

What does the intent_handle tool do? +

intent_handle. It is categorised as a Execute tool in the Homeassistant MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on intent_handle? +

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

What risk level is intent_handle? +

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

Can I rate-limit intent_handle? +

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

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

intent_handle is provided by the Homeassistant MCP server (robbrad/homeassistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.