set_group
A write tool on the Ha Nexus Agent MCP server.
This record as markdown: /tools/fistacho-ha-nexus-agent/set-group.md
What set_group does on Ha Nexus Agent
AI agents use set_group 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 set_group is rated Medium
The tool appears to create or modify group configurations in Home Assistant. This is a Write operation (creates/modifies data reversibly) rather than Execute or Destructive, since groups can be reconfigured or deleted. Severity is high because misconfiguration of groups could affect automation rules or entity organization across the smart home.
From the tool's definition Tool name is 'set_group' with empty description. In Home Assistant context, groups are configuration entities that logically aggregate devices/entities. Setting a group creates or modifies this aggregation, reversible through further edits or deletion.
Attacks that exploit this kind of access
The rule that runs set_group 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 set_group, this is the rule to start with:
set_group 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 set_group call is checked against it from then on.
Questions about set_group
set_group is a write tool on the Ha Nexus Agent MCP server. 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 set_group: 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.
set_group 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 set_group 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 set_group. 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.
set_group 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