notify_persistent_dismiss_all

Dismiss all persistent notifications.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/notify-persistent-dismiss-all.md

What notify_persistent_dismiss_all does on Ha Nexus Agent

AI agents call notify_persistent_dismiss_all 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_all is rated Critical

Dismissing all persistent notifications is an irreversible bulk action — once dismissed, those notifications are gone and cannot be recovered. This matches the Destructive category (irreversibly deletes/removes data).

From the tool's definition Dismiss all persistent notifications

Risk signalsBulk/mass operation — affects multiple targets

Questions about notify_persistent_dismiss_all

What does the notify_persistent_dismiss_all tool do? +

Dismiss all persistent notifications. 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.

How do I enforce a policy on notify_persistent_dismiss_all? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for notify_persistent_dismiss_all: 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.

What risk level is notify_persistent_dismiss_all? +

notify_persistent_dismiss_all is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit notify_persistent_dismiss_all? +

Yes. Add a rate_limit block to the notify_persistent_dismiss_all 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.

How do I block notify_persistent_dismiss_all completely? +

Set action: deny in the PolicyLayer policy for notify_persistent_dismiss_all. 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.

What MCP server provides notify_persistent_dismiss_all? +

notify_persistent_dismiss_all 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.