start_config_flow

What start_config_flow does on Ha Nexus Agent

AI agents invoke start_config_flow to trigger actions in Ha Nexus Agent. 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 start_config_flow is rated High

This tool executes an operation that triggers a configuration flow for Home Assistant integrations. While not immediately destructive, config flows can perform side effects such as connecting to external services, modifying authentication credentials, or changing system behavior. The impact depends entirely on which integration domain is targeted and what the flow does.

From the tool's definition 'Start a new config flow for the given integration domain' — initiates a dynamic configuration process for Home Assistant integrations, which can trigger external operations and modify system state depending on the integration type and arguments provided.

The rule that runs start_config_flow safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_config_flow, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_config_flow": {
      "limits": [
        {
          "counter": "start_config_flow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about start_config_flow