add_custom_repository
Add a custom HACS repository by URL + category (integration, plugin, theme, template, appdaemon, python_script).
This record as markdown: /tools/fistacho-ha-nexus-agent/add-custom-repository.md
What add_custom_repository does on Ha Nexus Agent
AI agents use add_custom_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 add_custom_repository is rated Medium
This tool creates and stores a new repository reference, which is reversible (can be removed later), making it Write rather than Execute or Destructive. However, severity is high because adding a malicious custom repository could enable code injection attacks on the Home Assistant instance — repositories marked as 'integration', 'appdaemon', or 'python_script' categories explicitly execute code.
From the tool's definition Tool description states 'Add a custom HACS repository' — a create/add operation that persists new configuration to the smart home system.
Attacks that exploit this kind of access
The rule that runs add_custom_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 add_custom_repository, this is the rule to start with:
add_custom_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 add_custom_repository call is checked against it from then on.
Questions about add_custom_repository
Add a custom HACS repository by URL + category (integration, plugin, theme, template, appdaemon, python_script). 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 add_custom_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.
add_custom_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 add_custom_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 add_custom_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.
add_custom_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