install_hacs_repository
Install a HACS repository, optionally pinning a specific version.
This record as markdown: /tools/fistacho-ha-nexus-agent/install-hacs-repository.md
What install_hacs_repository does on Ha Nexus Agent
AI agents invoke install_hacs_repository 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 install_hacs_repository is rated High
Installing a HACS (Home Assistant Community Store) repository executes an installation process that adds third-party code/integrations to the Home Assistant environment. This is an Execute-level action because it triggers external operations (downloading and installing software), with high severity since malicious or buggy third-party code could compromise the entire smart home system.
From the tool's definition Install a HACS repository, optionally pinning a specific version
Attacks that exploit this kind of access
The rule that runs install_hacs_repository 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 install_hacs_repository, this is the rule to start with:
install_hacs_repository 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 install_hacs_repository call is checked against it from then on.
Questions about install_hacs_repository
Install a HACS repository, optionally pinning a specific 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.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for install_hacs_repository: 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.
install_hacs_repository 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 install_hacs_repository 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 install_hacs_repository. 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.
install_hacs_repository 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