Clear all notifications
AI agents call clear_all_notifications to permanently remove resources in HC3 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing all notifications is a bulk, irreversible deletion of data. Once all notifications are cleared, they cannot be recovered, making this a Destructive action. The high severity reflects the bulk nature of the operation (all notifications), which an AI agent could misuse to wipe the entire notification history of a smart home system.
From the tool's definition 'Clear all notifications' — removes all notifications irreversibly
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all notifications. It is categorised as a Destructive tool in the HC3 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for clear_all_notifications: 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 HC3 MCP Server. Nothing to install.
clear_all_notifications 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 clear_all_notifications 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 clear_all_notifications. 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.
clear_all_notifications is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →