list_addons

List all installed add-ons with slug, name, state, version, update_available.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/list-addons.md

WHAT IT DOES

What list_addons does on Ha Nexus Agent

AI agents call list_addons to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_addons is rated Low

This tool performs a read-only query of installed Home Assistant add-ons. It retrieves metadata (slug, name, state, version, update availability) without creating, modifying, deleting, or executing any actions. The blast radius if misused is minimal — an attacker would only gain visibility into what add-ons are installed, not control over them.

From the tool's definition Tool name is 'list_addons' and description states it 'List all installed add-ons' — a pure query operation that retrieves and returns information about add-ons without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_addons Allowed

list_addons is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_addons": {}
  }
}

ALLOW ONLY 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 list_addons call is checked against it from then on.

FAQ

Questions about list_addons

What does the list_addons tool do? +

List all installed add-ons with slug, name, state, version, update_available. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_addons? +

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

list_addons is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_addons? +

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

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

list_addons 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 →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →