Critical Risk →

sb_delete_bucket

Delete a storage bucket from Supabase. The bucket must be empty before deletion. Use sb_delete_objects to remove files first.

Part of the Supabase MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@supabase-community/supabase-mcp Destructive Risk 4/5

AI agents may call sb_delete_bucket to permanently remove or destroy resources in Supabase. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call sb_delete_bucket in a loop, permanently destroying resources in Supabase. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

supabase.yaml
tools:
  sb_delete_bucket:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Supabase policy for all 63 tools.

Tool Name sb_delete_bucket
Category Destructive
MCP Server Supabase MCP Server
Risk Level Critical

View all 63 tools →

Agents calling destructive-class tools like sb_delete_bucket have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

sb_delete_bucket is one of the critical-risk operations in Supabase. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the sb_delete_bucket tool do? +

Delete a storage bucket from Supabase. The bucket must be empty before deletion. Use sb_delete_objects to remove files first.. It is categorised as a Destructive tool in the Supabase 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 sb_delete_bucket? +

Add a rule in your Intercept YAML policy under the tools section for sb_delete_bucket. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Supabase MCP server.

What risk level is sb_delete_bucket? +

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

Yes. Add a rate_limit block to the sb_delete_bucket rule in your Intercept 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 sb_delete_bucket completely? +

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

sb_delete_bucket is provided by the Supabase MCP server (@supabase-community/supabase-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Supabase

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.