apply_migration · Supabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What apply_migration does on Supabase MCP Server

AI agents invoke apply_migration to trigger actions in Supabase MCP Server. 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 IT NEEDS A POLICY

Why apply_migration needs a policy

This tool executes arbitrary SQL DDL operations (schema changes) against a database. While migrations are tracked, DDL operations can include DROP TABLE, ALTER TABLE, or other destructive schema changes.

From the tool's definition 'Applies a SQL migration to the database. SQL passed to this tool will be tracked within the database, so LLMs should use this for DDL operations (schema changes).'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

apply_migration Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "apply_migration": {
      "limits": [
        {
          "counter": "apply_migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Supabase MCP Server, so you can run agents against it safely.

FAQ

Questions about apply_migration

What does the apply_migration tool do? +

Applies a SQL migration to the database. SQL passed to this tool will be tracked within the database, so LLMs should use this for DDL operations (schema changes). It is categorised as a Execute tool in the Supabase MCP Server 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 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. 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 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.

// THE FULL RECORD

apply_migration is one line of Supabase MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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