notify_persistent_dismiss
Dismiss a persistent notification by its notification_id.
This record as markdown: /tools/fistacho-ha-nexus-agent/notify-persistent-dismiss.md
What notify_persistent_dismiss does on Ha Nexus Agent
AI agents call notify_persistent_dismiss to permanently remove resources in Ha Nexus Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why notify_persistent_dismiss is rated Critical
Dismissing a persistent notification is an irreversible action — once dismissed, the notification is removed and cannot be restored. This makes it Destructive rather than Write. Severity is medium because while the blast radius is limited (only notification data is lost, not critical system state), important alerts or reminders could be permanently lost if misused.
From the tool's definition Dismiss a persistent notification by its `notification_id`
Attacks that exploit this kind of access
The rule that runs notify_persistent_dismiss 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_dismiss, this is the rule to start with:
notify_persistent_dismiss is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every notify_persistent_dismiss call is checked against it from then on.
Questions about notify_persistent_dismiss
Dismiss a persistent notification by its notification_id. It is categorised as a Destructive tool in the Ha Nexus Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for notify_persistent_dismiss: 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_dismiss is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the notify_persistent_dismiss 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_dismiss. 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_dismiss 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