Delete all gateway notifications. Use this to clear error messages or warnings from the Plugwise gateway.
AI agents call delete_notification to permanently remove resources in Plugwise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of notification data from the Plugwise gateway. Although the data loss is limited in scope (notifications only, not device configs or settings), deletion operations that cannot be undone fall into the Destructive category.
From the tool's definition Tool name contains 'delete' and description states 'Delete all gateway notifications' — this irreversibly removes data (error messages and warnings) that cannot be undone.
Attacks that exploit this kind of access
Delete all gateway notifications. Use this to clear error messages or warnings from the Plugwise gateway. It is categorised as a Destructive tool in the Plugwise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Plugwise MCP Server MCP server in PolicyLayer and add a rule for delete_notification: 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 Plugwise MCP Server. Nothing to install.
delete_notification 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 delete_notification 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 delete_notification. 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.
delete_notification is provided by the Plugwise MCP Server MCP server (tommertom/plugwise-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 →