update_addon

Update an add-on to the latest available version.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/update-addon.md

WHAT IT DOES

What update_addon does on Ha Nexus Agent

AI agents invoke update_addon 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.

RISK

Why update_addon is rated High

Updating an add-on triggers an external operation that downloads and installs new software on the Home Assistant system. This is not a simple data write — it executes an installation/upgrade process that modifies system state, potentially changes behavior, and could introduce breaking changes.

From the tool's definition Update an add-on to the latest available version

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_addon 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 update_addon, this is the rule to start with:

update_addon Rate-limited

update_addon 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": {
    "update_addon": {
      "limits": [
        {
          "counter": "update_addon_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every update_addon call is checked against it from then on.

FAQ

Questions about update_addon

What does the update_addon tool do? +

Update an add-on to the latest available version. 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.

How do I enforce a policy on update_addon? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for update_addon: 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.

What risk level is update_addon? +

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

Can I rate-limit update_addon? +

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

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

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

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →