list_migrations
Lists all migrations in the database.
This record as markdown: /tools/supabase/list-migrations.md
What list_migrations does on Supabase
AI agents call list_migrations 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_migrations is rated Low
This tool retrieves and displays migration history metadata without executing, modifying, or deleting anything. It is a read-only query operation with minimal blast radius if misused by an AI agent. The low severity reflects that listing migrations poses no risk of unintended data loss or system changes.
From the tool's definition Tool name and description indicate it 'Lists all migrations in the database' - a retrieval operation with no data modification.
Attacks that exploit this kind of access
The rule that runs list_migrations 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_migrations, this is the rule to start with:
list_migrations 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_migrations call is checked against it from then on.
Questions about list_migrations
Lists all migrations in the database. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
list_migrations 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_migrations: 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_migrations 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_migrations 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_migrations. 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_migrations 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