assign_label_to_entity
Assign a label to an entity (preserves existing labels).
This record as markdown: /tools/fistacho-ha-nexus-agent/assign-label-to-entity.md
What assign_label_to_entity does on Ha Nexus Agent
AI agents use assign_label_to_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 assign_label_to_entity is rated Medium
This tool creates or modifies labels on Home Assistant entities. It is Write-category because it changes data (entity labels) reversibly without deleting or destroying anything. The scope is limited to label metadata on a single entity, making severity low. Confidence is high due to clear description and straightforward operation.
From the tool's definition Assign a label to an entity (preserves existing labels) — modifies entity metadata by adding/assigning labels, a reversible operation.
Attacks that exploit this kind of access
The rule that runs assign_label_to_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 assign_label_to_entity, this is the rule to start with:
assign_label_to_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every assign_label_to_entity call is checked against it from then on.
Questions about assign_label_to_entity
Assign a label to an entity (preserves existing labels). 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.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for assign_label_to_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.
assign_label_to_entity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the assign_label_to_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.
Set action: deny in the PolicyLayer policy for assign_label_to_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.
assign_label_to_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.
This server
Across the catalogue