input_text_control · Homeassistant MCP: Risk & Policy

WHAT IT DOES

What input_text_control does on Homeassistant

AI agents use input_text_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_text_control needs a policy

Based on the name, this tool likely controls Home Assistant input_text entities, which are writable helper entities used to store text values. Setting these values is a Write operation. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'input_text_control' suggests setting/modifying text input helpers in Home Assistant; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

input_text_control Rate-limited

input_text_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_text_control": {
      "limits": [
        {
          "counter": "input_text_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_text_control

What does the input_text_control tool do? +

input_text_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_text_control? +

Register the Homeassistant MCP server in PolicyLayer and add a rule for input_text_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_text_control? +

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

Can I rate-limit input_text_control? +

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

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

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