reset_branch
Resets migrations of a development branch. Any untracked data or schema changes will be lost.
This record as markdown: /tools/supabase/reset-branch.md
What reset_branch does on Supabase
AI agents call reset_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 | — | |
migration_version | string | — | Reset your development branch to a specific migration version. |
Parameters from the server's own tool schema.
Why reset_branch is rated Critical
This tool irreversibly deletes or overwrites data (untracked data and schema changes). It matches the Destructive category definition: actions that cannot be undone. While scoped to a development branch (limiting blast radius vs. production), the operation itself is fundamentally destructive. Severity is high rather than critical because it affects development infrastructure, not production systems or financial data.
From the tool's definition Tool description explicitly states 'Any untracked data or schema changes will be lost' — indicating irreversible deletion of database state. The operation 'resets migrations' on a development branch, which cannot be undone without manual recovery.
Attacks that exploit this kind of access
The rule that runs reset_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 reset_branch, this is the rule to start with:
reset_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 reset_branch call is checked against it from then on.
Questions about reset_branch
Resets migrations of a development branch. Any untracked data or schema changes will be lost. 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.
reset_branch accepts 2 parameters: branch_id, migration_version. 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 reset_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.
reset_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 reset_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 reset_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.
reset_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