Delete file from Supabase Storage
AI agents call supabase.storage_delete to permanently remove resources in MCP Fullstack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on stored files. Even though it operates within a single storage bucket rather than across an entire database, file deletion cannot be undone without backup recovery procedures. This makes it Destructive rather than Write.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete file from Supabase Storage' — this irreversibly removes data from persistent storage.
Attacks that exploit this kind of access
Delete file from Supabase Storage. It is categorised as a Destructive tool in the MCP Fullstack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Fullstack MCP server in PolicyLayer and add a rule for supabase.storage_delete: 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 MCP Fullstack. Nothing to install.
supabase.storage_delete 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.storage_delete 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.storage_delete. 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.storage_delete is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). 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 →