supabase_apply_migration

Apply a named, tracked migration to a Supabase project's database via the Management API.

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/supabase-apply-migration.md

WHAT IT DOES

What supabase_apply_migration does on UnClick

AI agents use supabase_apply_migration to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.

Parameter	Type	Required	Description
`sql`	string	Yes	The migration SQL.
`name`	string	Yes	Short snake_case migration name.
`api_key`	string	—	Legacy token alias.
`project_ref`	string	Yes	Supabase project ref.
`access_token`	string	—	Optional Supabase access token. Omit to use the connected login.

Parameters from the server's own tool schema.

RISK

Why supabase_apply_migration is rated Medium

An AI agent can call supabase_apply_migration faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.

Risk signalsAccepts freeform code/query input (sql) · Handles credentials or secrets (access_token)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs supabase_apply_migration safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_apply_migration, this is the rule to start with:

supabase_apply_migration Rate-limited

supabase_apply_migration stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "supabase_apply_migration": {
      "limits": [
        {
          "counter": "supabase_apply_migration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every supabase_apply_migration call is checked against it from then on.

FAQ

Questions about supabase_apply_migration

What does the supabase_apply_migration tool do? +

Apply a named, tracked migration to a Supabase project's database via the Management API. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does supabase_apply_migration accept? +

supabase_apply_migration accepts 5 parameters: sql, name, api_key, project_ref, access_token. Required: sql, name, project_ref. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on supabase_apply_migration? +

Register the UnClick MCP server in PolicyLayer and add a rule for supabase_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 UnClick. Nothing to install.

What risk level is supabase_apply_migration? +

supabase_apply_migration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit supabase_apply_migration? +

Yes. Add a rate_limit block to the supabase_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 supabase_apply_migration completely? +

Set action: deny in the PolicyLayer policy for supabase_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 supabase_apply_migration? +

supabase_apply_migration is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →