merge_branch
Merges migrations and edge functions from a development branch to production.
This record as markdown: /tools/supabase/merge-branch.md
What merge_branch does on Supabase
AI agents invoke merge_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 merge_branch is rated High
Merging to production triggers schema migrations and deploys edge functions, which are irreversible operational changes to a live environment. While not purely destructive (it's additive/promotional in nature), it executes complex database migration scripts and code deployments with production-level blast radius.
From the tool's definition Merges migrations and edge functions from a development branch to production
Attacks that exploit this kind of access
The rule that runs merge_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 merge_branch, this is the rule to start with:
merge_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 merge_branch call is checked against it from then on.
Questions about merge_branch
Merges migrations and edge functions from a development branch to production. 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.
merge_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 merge_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.
merge_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 merge_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 merge_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.
merge_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