Creates a development branch with migrations from production branch.
AI agents use create_branch to create or update resources in Supabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase MCP Server environment.
This tool creates new infrastructure (a development branch with migrations), which modifies the state of the Supabase project. It is a write operation because it creates data/resources, but not destructive because branches are ephemeral and deletable.
From the tool's definition Tool description states it 'Creates a development branch' — the verb 'creates' is a reversible write operation. Branches can be deleted (as evidenced by the sibling tool 'delete_branch'), making this non-destructive.
Attacks that exploit this kind of access
Creates a development branch with migrations from production branch. It is categorised as a Write tool in the Supabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_branch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →