update_category
Update a category via WS config/category_registry/update.
This record as markdown: /tools/fistacho-ha-nexus-agent/update-category.md
What update_category does on Ha Nexus Agent
AI agents use update_category 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 update_category is rated Medium
This tool modifies Home Assistant's category registry configuration. It is a Write operation because it updates/modifies data without permanently destroying it—categories can be revised or reconfigured. Severity is medium because misconfiguration of categories could disrupt smart home organization and potentially affect automation rule targeting, but it does not delete data irreversibly or execute arbitrary commands.
From the tool's definition Tool name 'update_category' and description 'Update a category via WS `config/category_registry/update`' indicate modification of configuration data. The use of 'update' is a classic Write operation that modifies existing data reversibly.
Attacks that exploit this kind of access
The rule that runs update_category 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 update_category, this is the rule to start with:
update_category 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 update_category call is checked against it from then on.
Questions about update_category
Update a category via WS config/category_registry/update. 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 update_category: 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.
update_category 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 update_category 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 update_category. 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.
update_category 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