remove_device

Remove a device from a specific config entry.

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/remove-device.md

WHAT IT DOES

What remove_device does on Ha Nexus Agent

AI agents call remove_device 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 remove_device is rated Critical

Device removal is a destructive action that cannot be undone without manual reconfiguration. It severs the device's integration with Home Assistant and its automations/scenes. While not as critical as deleting user data or financial records, it permanently alters the smart home setup and could break dependent automations.

From the tool's definition Tool description states 'Remove a device from a specific config entry' — this is an irreversible deletion operation that eliminates a device configuration from Home Assistant.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

remove_device Hidden

remove_device 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": [
    "remove_device"
  ]
}

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 remove_device call is checked against it from then on.

FAQ

Questions about remove_device

What does the remove_device tool do? +

Remove a device from a specific config entry. 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 remove_device? +

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

remove_device 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 remove_device? +

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

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

remove_device 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

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →