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.
Attacks that exploit this kind of access
The rule that runs Delete_Bundle_Notification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Delete_Bundle_Notification, this is the rule to start with:
Delete_Bundle_Notification is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Files Com, apply this rule, and every Delete_Bundle_Notification call is checked against it from then on.
Questions about Delete_Bundle_Notification
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.
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.
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.
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.
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.
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.
Across the catalogue