remove_group
Remove a Home Assistant entity group. Set confirm=True to proceed.
This record as markdown: /tools/fistacho-ha-nexus-agent/remove-group.md
What remove_group does on Ha Nexus Agent
AI agents call remove_group 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.
Why remove_group is rated Critical
This tool permanently deletes a Home Assistant group, which is an irreversible operation. Removal of groups can break automations, scenes, and dashboard configurations that depend on them. While not as severe as deleting all devices, the destruction of configuration state and potential cascading failures justify 'Destructive' classification (more severe than Write).
From the tool's definition Tool name is 'remove_group' with description stating 'Remove a Home Assistant entity group.' The word 'Remove' combined with the action of deleting a group is irreversible — once removed, the group configuration and any associated automation or dashboard…
Attacks that exploit this kind of access
The rule that runs remove_group 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 remove_group, this is the rule to start with:
remove_group is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every remove_group call is checked against it from then on.
Questions about remove_group
Remove a Home Assistant entity group. Set confirm=True to proceed. 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.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for remove_group: 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.
remove_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_group 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 remove_group. 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.
remove_group 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.
Across the catalogue