disable_integration

Disable an integration config entry without removing it.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/disable-integration.md

WHAT IT DOES

What disable_integration does on Ha Nexus Agent

AI agents use disable_integration to create or update resources in Ha Nexus Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ha Nexus Agent environment.

RISK

Why disable_integration is rated Medium

Disabling an integration deactivates it (potentially taking smart home devices offline) but is reversible since the config entry is not removed. This is a Write action with high severity given the blast radius — disabling the wrong integration could render home automation systems non-functional.

From the tool's definition Disable an integration config entry without removing it

Attacks that exploit this kind of access

RECOMMENDED RULE

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

disable_integration Rate-limited

disable_integration stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disable_integration": {
      "limits": [
        {
          "counter": "disable_integration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about disable_integration

What does the disable_integration tool do? +

Disable an integration config entry without removing it. It is categorised as a Write tool in the Ha Nexus Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disable_integration? +

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

disable_integration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disable_integration? +

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

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

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

KEEP EXPLORING

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

This server

All 276 Ha Nexus Agent tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →