Resets migrations of a development branch to a prior version.
AI agents call reset_branch 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.
This tool performs an irreversible action on database migrations. Resetting a branch to a prior version destroys the current migration state and cannot be easily undone without manual recovery. While it targets a development branch (lower blast radius than production), the inability to undo the operation and potential for data loss places it in the Destructive category.
From the tool's definition Tool description states it 'Resets migrations of a development branch to a prior version.' Resetting migrations is an irreversible operation that rolls back schema changes and potentially loses committed migration state.
Attacks that exploit this kind of access
Resets migrations of a development branch to a prior version. 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 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 MCP Server. 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 MCP server (pipethedev/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 →