Critical Risk →

pluggedin_delete_notification

Delete a notification from the Plugged.in system

How to control pluggedin_delete_notification ↓

AI agents call pluggedin_delete_notification to permanently remove resources in Pluggedin Mcp Proxy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The tool performs an irreversible deletion of data (a notification). While the blast radius is limited to a single notification rather than bulk data, deletion operations are categorized as Destructive per the classification rules. Severity is medium rather than high because notifications are typically non-critical data with limited downstream impact compared to core user data or system configurations.

From the tool's definition Tool name contains 'delete' and description states 'Delete a notification from the Plugged.in system' — this is an irreversible deletion operation.

Documented attack patterns abuse exactly the kind of access pluggedin_delete_notification gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Pluggedin Mcp Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for pluggedin_delete_notification:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "pluggedin_delete_notification"
  ]
}

pluggedin_delete_notification disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Pluggedin Mcp Proxy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the pluggedin_delete_notification tool do? +

Delete a notification from the Plugged.in system. It is categorised as a Destructive tool in the Pluggedin Mcp Proxy 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 pluggedin_delete_notification? +

Register the Pluggedin Mcp Proxy MCP server in PolicyLayer and add a rule for pluggedin_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 Pluggedin Mcp Proxy. Nothing to install.

What risk level is pluggedin_delete_notification? +

pluggedin_delete_notification 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 pluggedin_delete_notification? +

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

How do I block pluggedin_delete_notification completely? +

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

What MCP server provides pluggedin_delete_notification? +

pluggedin_delete_notification is provided by the Pluggedin Mcp Proxy MCP server (veriteknik/pluggedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pluggedin Mcp Proxy tool call.

Deterministic rules across all 27 Pluggedin Mcp Proxy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

27 Pluggedin Mcp Proxy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.