remove_integration

Remove (uninstall) an integration 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-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.

Questions about remove_integration

What does the remove_integration tool do? +

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.

How do I enforce a policy on remove_integration? +

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.

What risk level is remove_integration? +

remove_integration 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_integration? +

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.

How do I block remove_integration completely? +

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.

What MCP server provides remove_integration? +

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.

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