install_hacs_repository

Install a HACS repository, optionally pinning a specific 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/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

Questions about install_hacs_repository

What does the install_hacs_repository tool do? +

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.

How do I enforce a policy on install_hacs_repository? +

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.

What risk level is install_hacs_repository? +

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

Can I rate-limit install_hacs_repository? +

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.

How do I block install_hacs_repository completely? +

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.

What MCP server provides install_hacs_repository? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.