delete_branch
Deletes a development branch.
This record as markdown: /tools/supabase/delete-branch.md
What delete_branch does on Supabase
AI agents call delete_branch to permanently remove resources in Supabase, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
branch_id | string | — |
Parameters from the server's own tool schema.
Why delete_branch is rated Critical
Deletion operations are inherently destructive and cannot be undone. Removing a development branch eliminates the branch and its associated data/state. This is classified as Destructive rather than Write because the action is irreversible.
From the tool's definition Tool name 'delete_branch' and description 'Deletes a development branch' indicate irreversible deletion of a branch resource.
Attacks that exploit this kind of access
The rule that runs delete_branch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_branch, this is the rule to start with:
delete_branch 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 Supabase, apply this rule, and every delete_branch call is checked against it from then on.
Questions about delete_branch
Deletes a development branch. 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.
delete_branch accepts 1 parameter: branch_id. The full parameter table on this page comes from the server's own tool schema.
Register the Supabase MCP server in PolicyLayer and add a rule for delete_branch: 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. Nothing to install.
delete_branch 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_branch 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_branch. 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_branch is provided by the Supabase MCP server (@modelcontextprotocol/server-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase, and thousands of servers like it.
Across the catalogue