New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

apply_migration

Advanced migrations with validation

SERVERSupabase MCP Server - Self-Hosted Edition SOURCEabdqum/supabase-mcp-selfhosted
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/apply-migration.md

What apply_migration does on Supabase MCP Server - Self-Hosted Edition

AI agents invoke apply_migration to trigger actions in Supabase MCP Server - Self-Hosted Edition. 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.

Why apply_migration is rated High

Applying a database migration executes schema changes (DDL statements like ALTER TABLE, CREATE TABLE, DROP TABLE, etc.) against the database. While it includes validation, migrations can be irreversible and have wide blast radius. The description is minimal but the tool name combined with the server context (database migrations) indicates execution of potentially destructive schema changes.

From the tool's definition 'apply_migration' with description 'Advanced migrations with validation'

Questions about apply_migration

What does the apply_migration tool do? +

Advanced migrations with validation. It is categorised as a Execute tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on apply_migration? +

Register the Supabase MCP Server - Self-Hosted Edition 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 MCP Server - Self-Hosted Edition. Nothing to install.

What risk level is apply_migration? +

apply_migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit apply_migration? +

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.

How do I block apply_migration completely? +

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.

What MCP server provides apply_migration? +

apply_migration is provided by the Supabase MCP Server - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Supabase MCP Server - Self-Hosted Edition's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.