enable_entity

Re-enable a disabled entity.

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/enable-entity.md

WHAT IT DOES

What enable_entity does on Ha Nexus Agent

AI agents use enable_entity 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 enable_entity is rated Medium

This tool modifies Home Assistant entity state by re-enabling a previously disabled entity. It is a reversible Write operation—the entity can be disabled again. It carries medium severity because misuse could enable unintended smart home automations or controls, but the action is not destructive and can be easily undone.

From the tool's definition Tool name 'enable_entity' and description 'Re-enable a disabled entity' indicate modification of entity state in Home Assistant. This reverses a prior disable action, changing configuration or operational state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

enable_entity Rate-limited

enable_entity 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": {
    "enable_entity": {
      "limits": [
        {
          "counter": "enable_entity_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 enable_entity call is checked against it from then on.

FAQ

Questions about enable_entity

What does the enable_entity tool do? +

Re-enable a disabled entity. 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 enable_entity? +

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

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

Can I rate-limit enable_entity? +

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

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

enable_entity 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 →