rebase_branch
Rebases a development branch on production. This will effectively run any newer migrations from production onto this branch to help handle migration drift.
This record as markdown: /tools/supabase/rebase-branch.md
What rebase_branch does on Supabase
AI agents invoke rebase_branch to trigger actions in Supabase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
branch_id | string | — |
Parameters from the server's own tool schema.
Why rebase_branch is rated High
This tool executes database migrations on a branch, which constitutes code execution (migration scripts run against a database). While the description frames it as a helpful drift-resolution operation, the actual effect is to execute arbitrary migration code that could modify schema, data, or both. This goes beyond simple Write (reversible data changes) because migrations can include destructive operations.
From the tool's definition Tool performs 'rebases a development branch on production' and 'run any newer migrations from production onto this branch'.
Attacks that exploit this kind of access
The rule that runs rebase_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 rebase_branch, this is the rule to start with:
rebase_branch stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every rebase_branch call is checked against it from then on.
Questions about rebase_branch
Rebases a development branch on production. This will effectively run any newer migrations from production onto this branch to help handle migration drift. It is categorised as a Execute tool in the Supabase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
rebase_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 rebase_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.
rebase_branch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rebase_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 rebase_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.
rebase_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