remove_integration
Remove (uninstall) an integration config entry.
This record as markdown: /tools/fistacho-ha-nexus-agent/remove-integration.md
What remove_integration does on Ha Nexus Agent
AI agents call remove_integration 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_integration is rated Critical
Removing an integration config entry is an irreversible operation that destroys configuration state. Once deleted, the integration settings cannot be automatically recovered without manual reconfiguration. This represents a destructive action with significant blast radius in a smart home context, as it disables functionality and could affect dependent automations or scenes.
From the tool's definition Tool name 'remove_integration' combined with description 'Remove (uninstall) an integration config entry' indicates irreversible deletion of configuration data.
Attacks that exploit this kind of access
The rule that runs remove_integration 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_integration, this is the rule to start with:
remove_integration 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_integration call is checked against it from then on.
Questions about remove_integration
Remove (uninstall) an integration 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.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for remove_integration: 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_integration 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_integration 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_integration. 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_integration 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