disable_entity

Disable an entity in the registry.

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

What disable_entity does on Ha Nexus Agent

AI agents use disable_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.

Why disable_entity is rated Medium

This tool modifies the state or configuration of a smart home entity by disabling it in the registry. While this is a reversible operation (entities can be re-enabled), it does alter system state and could disrupt automations or device control if misused. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely retrieve information (Read).

From the tool's definition Tool name 'disable_entity' and description 'Disable an entity in the registry' indicate modification of entity state/configuration. The action is reversible (entities can be re-enabled), and affects smart home automation behavior rather than causing data loss.

Questions about disable_entity

What does the disable_entity tool do? +

Disable an entity in the registry. 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_entity? +

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

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

Can I rate-limit disable_entity? +

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

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

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

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

Across the catalogue

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