Delete file(s) from storage
AI agents call supabase_delete_file to permanently remove resources in Supabase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
File deletion is a destructive operation that cannot be undone. Deleting files from storage permanently removes data with no recovery mechanism (unless backups exist outside this tool's scope). While the blast radius is somewhat limited to files rather than database records, the irreversible nature and potential loss of user-critical data (documents, media, backups) justifies 'high' severity.
From the tool's definition Tool name 'supabase_delete_file' and description 'Delete file(s) from storage' explicitly indicate irreversible deletion of files.
Attacks that exploit this kind of access
Delete file(s) from storage. It is categorised as a Destructive tool in the Supabase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for supabase_delete_file: 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 Supabase MCP Server. Nothing to install.
supabase_delete_file 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 supabase_delete_file 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 supabase_delete_file. 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.
supabase_delete_file is provided by the Supabase MCP Server MCP server (sweir1/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →