add_custom_repository

Add a custom HACS repository by URL + category (integration, plugin, theme, template, appdaemon, python_script).

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent
Medium RISK CLASS
Category Write
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/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.

Questions about add_custom_repository

What does the add_custom_repository tool do? +

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.

How do I enforce a policy on add_custom_repository? +

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.

What risk level is add_custom_repository? +

add_custom_repository is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_custom_repository? +

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.

How do I block add_custom_repository completely? +

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.

What MCP server provides add_custom_repository? +

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.

// 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.