rebase_branch · Supabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What rebase_branch does on Supabase MCP Server

AI agents invoke rebase_branch to trigger actions in Supabase MCP Server. 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.

WHY IT NEEDS A POLICY

Why rebase_branch needs a policy

Rebasing a branch involves replaying migrations and altering database state in a potentially complex, partially-irreversible operation. It triggers a sequence of database migration operations against a branch, and if it fails mid-way or applies incorrectly, it can corrupt the branch schema.

From the tool's definition Rebases development branch on production to handle migration drift

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rebase_branch Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rebase_branch": {
      "limits": [
        {
          "counter": "rebase_branch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Supabase MCP Server, so you can run agents against it safely.

FAQ

Questions about rebase_branch

What does the rebase_branch tool do? +

Rebases development branch on production to handle migration drift. It is categorised as a Execute tool in the Supabase MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rebase_branch? +

Register the Supabase MCP Server 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 MCP Server. Nothing to install.

What risk level is rebase_branch? +

rebase_branch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rebase_branch? +

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.

How do I block rebase_branch completely? +

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.

What MCP server provides rebase_branch? +

rebase_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.