New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

Delete_Bundle_Notification

Delete Share Link Notification

SERVERFiles Com SOURCEfiles-com-mcp
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/com-files-python-mcp/delete-bundle-notification.md

What Delete_Bundle_Notification does on Files Com

AI agents call Delete_Bundle_Notification to permanently remove resources in Files Com, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why Delete_Bundle_Notification is rated Critical

This tool performs a destructive operation by deleting notification data. Although the blast radius is narrower than deleting files or users (confined to a single notification record), the action is irreversible and represents permanent data loss.

From the tool's definition Tool name 'Delete_Bundle_Notification' and description 'Delete Share Link Notification' indicate irreversible deletion of a notification record. The 'Delete' operation on a notification entity cannot be undone.

Questions about Delete_Bundle_Notification

What does the Delete_Bundle_Notification tool do? +

Delete Share Link Notification. It is categorised as a Destructive tool in the Files Com 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 Delete_Bundle_Notification? +

Register the Files Com MCP server in PolicyLayer and add a rule for Delete_Bundle_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 Files Com. Nothing to install.

What risk level is Delete_Bundle_Notification? +

Delete_Bundle_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 Delete_Bundle_Notification? +

Yes. Add a rate_limit block to the Delete_Bundle_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 Delete_Bundle_Notification completely? +

Set action: deny in the PolicyLayer policy for Delete_Bundle_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 Delete_Bundle_Notification? +

Delete_Bundle_Notification is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Files Com, 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 Files Com'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.