list_branches
Lists all development branches of a Supabase project. This will return branch details including status which you can use to check when operations like merge/rebase/reset complete.
This record as markdown: /tools/supabase/list-branches.md
What list_branches does on Supabase
AI agents call list_branches to retrieve information from Supabase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | — |
Parameters from the server's own tool schema.
Why list_branches is rated Low
This tool queries and retrieves branch metadata from a Supabase project. It performs no data modification, deletion, or external operations—purely informational retrieval. The low severity reflects minimal blast radius: exposing branch lists to an AI agent poses negligible risk.
From the tool's definition Tool description explicitly states 'Lists all development branches' and 'return branch details', which are read-only operations that retrieve information without modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_branches 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 list_branches, this is the rule to start with:
list_branches is read-only, so it stays allowed. 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 list_branches call is checked against it from then on.
Questions about list_branches
Lists all development branches of a Supabase project. This will return branch details including status which you can use to check when operations like merge/rebase/reset complete. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
list_branches accepts 1 parameter: project_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 list_branches: 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.
list_branches is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_branches 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 list_branches. 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.
list_branches 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.
This server
Across the catalogue