input_datetime_control · Homeassistant MCP: Risk & Policy

WHAT IT DOES

What input_datetime_control does on Homeassistant

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

WHY IT NEEDS A POLICY

Why input_datetime_control needs a policy

Based on the tool name, this likely reads or writes input_datetime helper entities in Home Assistant (setting date/time values). The 'control' suffix implies it can modify state, placing it in Write. Severity is medium because misconfiguration of datetime inputs could affect automations and schedules. Confidence is low due to the empty description.

From the tool's definition Tool name 'input_datetime_control' suggests controlling/setting datetime input entities in Home Assistant; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

input_datetime_control Rate-limited

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

FAQ

Questions about input_datetime_control

What does the input_datetime_control tool do? +

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

How do I enforce a policy on input_datetime_control? +

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

What risk level is input_datetime_control? +

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

Can I rate-limit input_datetime_control? +

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

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

input_datetime_control 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.