notify_persistent_create
Create or replace a persistent notification in the HA UI.
This record as markdown: /tools/fistacho-ha-nexus-agent/notify-persistent-create.md
What notify_persistent_create does on Ha Nexus Agent
AI agents use notify_persistent_create 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 notify_persistent_create is rated Medium
This tool creates or modifies persistent notifications in Home Assistant's UI. It is a Write operation because it creates new data (notifications) or updates existing ones in a reversible manner. Notifications can be dismissed or replaced, so the action is not destructive.
From the tool's definition Tool description states 'Create or replace a persistent notification in the HA UI' — a create/replace operation that modifies UI state reversibly.
Attacks that exploit this kind of access
The rule that runs notify_persistent_create 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 notify_persistent_create, this is the rule to start with:
notify_persistent_create 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 notify_persistent_create call is checked against it from then on.
Questions about notify_persistent_create
Create or replace a persistent notification in the HA UI. 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 notify_persistent_create: 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.
notify_persistent_create 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 notify_persistent_create 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 notify_persistent_create. 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.
notify_persistent_create 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