High Risk →

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.

Part of the Supabase Godmode MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

ubiq/supabase-godmode Execute Risk 3/5

AI agents invoke rebase_branch to trigger processes or run actions in Supabase Godmode. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

rebase_branch can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

ubiq-supabase-godmode.yaml
tools:
  rebase_branch:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Supabase Godmode policy for all 29 tools.

Tool Name rebase_branch
Category Execute
Risk Level High

View all 29 tools →

Agents calling execute-class tools like rebase_branch have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

rebase_branch is one of the high-risk operations in Supabase Godmode. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the rebase_branch tool do? +

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 Godmode 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? +

Add a rule in your Intercept YAML policy under the tools section for rebase_branch. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Supabase Godmode MCP server.

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 Intercept 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 Intercept 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 Godmode MCP server (ubiq/supabase-godmode). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Supabase Godmode

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.