uninstall_hacs_repository

Uninstall a HACS repository by id.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/uninstall-hacs-repository.md

WHAT IT DOES

What uninstall_hacs_repository does on Ha Nexus Agent

AI agents call uninstall_hacs_repository to permanently remove resources in Ha Nexus Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why uninstall_hacs_repository is rated Critical

Uninstalling a HACS (Home Assistant Community Store) repository is an irreversible action that removes custom integrations, automations, or other components from the smart home system. Once uninstalled, the functionality and any associated configurations dependent on that repository are lost.

From the tool's definition Tool name 'uninstall_hacs_repository' and description 'Uninstall a HACS repository by id' indicate irreversible removal of installed software/integrations from a Home Assistant system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uninstall_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 uninstall_hacs_repository, this is the rule to start with:

uninstall_hacs_repository Hidden

uninstall_hacs_repository is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "uninstall_hacs_repository"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every uninstall_hacs_repository call is checked against it from then on.

FAQ

Questions about uninstall_hacs_repository

What does the uninstall_hacs_repository tool do? +

Uninstall a HACS repository by id. It is categorised as a Destructive tool in the Ha Nexus Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on uninstall_hacs_repository? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for uninstall_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 uninstall_hacs_repository? +

uninstall_hacs_repository is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit uninstall_hacs_repository? +

Yes. Add a rate_limit block to the uninstall_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 uninstall_hacs_repository completely? +

Set action: deny in the PolicyLayer policy for uninstall_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 uninstall_hacs_repository? +

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

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →