Delete_Bundle

Delete Share Link

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.md

WHAT IT DOES

What Delete_Bundle does on Files Com

AI agents call Delete_Bundle 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.

RISK

Why Delete_Bundle is rated Critical

Deleting a share link (bundle) is an irreversible operation that removes access permissions and cannot be undone without recreating the bundle. This meets the Destructive category definition. Severity is high because deletion of sharing infrastructure could disrupt legitimate access workflows, though it does not directly impact core data or financial systems.

From the tool's definition Tool name 'Delete_Bundle' combined with description 'Delete Share Link' indicates irreversible deletion of a share link resource. The verb 'Delete' is explicitly destructive.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs Delete_Bundle 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, this is the rule to start with:

Delete_Bundle Hidden

Delete_Bundle is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "Delete_Bundle"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Files Com, apply this rule, and every Delete_Bundle call is checked against it from then on.

FAQ

Questions about Delete_Bundle

What does the Delete_Bundle tool do? +

Delete Share Link. 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? +

Register the Files Com MCP server in PolicyLayer and add a rule for Delete_Bundle: 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? +

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

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

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

Delete_Bundle 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.

KEEP EXPLORING

More on Files Com, and thousands of servers like it.

This server

All 68 Files Com tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →