update_hacs_repository
Update a HACS repository to its latest available version.
This record as markdown: /tools/fistacho-ha-nexus-agent/update-hacs-repository.md
What update_hacs_repository does on Ha Nexus Agent
AI agents use update_hacs_repository to create or update resources in Ha Nexus Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ha Nexus Agent environment.
Why update_hacs_repository is rated Medium
This tool modifies repository configuration and version state, fitting the Write category (creates or modifies data reversibly). The severity is high because uncontrolled repository updates in a smart home system could introduce breaking changes, bugs, or security issues that disrupt device automation and home control.
From the tool's definition Tool name 'update_hacs_repository' and description 'Update a HACS repository to its latest available version' indicate a reversible modification operation on repository state, changing its version.
Attacks that exploit this kind of access
The rule that runs update_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 update_hacs_repository, this is the rule to start with:
update_hacs_repository stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 update_hacs_repository call is checked against it from then on.
Questions about update_hacs_repository
Update a HACS repository to its latest available version. It is categorised as a Write tool in the Ha Nexus Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for update_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.
update_hacs_repository is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
This server
Across the catalogue