apply_migration
Applies a migration to the database. Use this when executing DDL operations. Do not hardcode references to generated IDs in data migrations.
This record as markdown: /tools/supabase/apply-migration.md
What apply_migration does on Supabase
AI agents invoke apply_migration to trigger actions in Supabase. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | The name of the migration in snake_case |
query | string | — | The SQL query to apply |
project_id | string | — |
Parameters from the server's own tool schema.
Why apply_migration is rated High
Applying a database migration executes DDL operations (CREATE, ALTER, DROP, etc.) against the database schema. While some DDL is reversible, migrations can include destructive schema changes (DROP TABLE, DROP COLUMN) and are generally difficult to undo safely.
From the tool's definition 'Applies a migration to the database. Use this when executing DDL operations.'
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs apply_migration 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 apply_migration, this is the rule to start with:
apply_migration 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every apply_migration call is checked against it from then on.
Questions about apply_migration
Applies a migration to the database. Use this when executing DDL operations. Do not hardcode references to generated IDs in data migrations. It is categorised as a Execute tool in the Supabase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
apply_migration accepts 3 parameters: name, query, 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 apply_migration: 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.
apply_migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the apply_migration 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 apply_migration. 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.
apply_migration 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.
Across the catalogue