upload_device
OTA flash compiled firmware to an ESPHome device via Dashboard API.
This record as markdown: /tools/fistacho-ha-nexus-agent/upload-device.md
What upload_device does on Ha Nexus Agent
AI agents invoke upload_device 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 upload_device is rated High
Flashing firmware to a device via OTA (Over-The-Air) is an execution operation that pushes new code onto hardware. It is not merely writing data — it triggers a physical firmware update process on an embedded device. Misuse could brick a device, introduce malicious firmware, or disrupt smart home operations.
From the tool's definition OTA flash compiled firmware to an ESPHome device via Dashboard API
Attacks that exploit this kind of access
The rule that runs upload_device 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 upload_device, this is the rule to start with:
upload_device 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every upload_device call is checked against it from then on.
Questions about upload_device
OTA flash compiled firmware to an ESPHome device via Dashboard API. It is categorised as a Execute tool in the Ha Nexus Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for upload_device: 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 Ha Nexus Agent. Nothing to install.
upload_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the upload_device 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.
Set action: deny in the PolicyLayer policy for upload_device. 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.
upload_device is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
Across the catalogue