validate_migration

A execute tool on the Supabase MCP Server - Self-Hosted Edition MCP server.

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/validate-migration.md

WHAT IT DOES

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

AI agents invoke validate_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.

RISK

Why validate_migration is rated High

Based on the tool name, 'validate_migration' likely checks or validates a database migration without applying it, which would be a Read/Execute operation. In the context of a Supabase MCP server with migration tools like 'apply_migration' and 'auto_migrate' as siblings, validation typically involves analyzing migration scripts for correctness. Without a description, confidence is low.

From the tool's definition Tool name: validate_migration; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs validate_migration safely

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

validate_migration Rate-limited

validate_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": {
    "validate_migration": {
      "limits": [
        {
          "counter": "validate_migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every validate_migration call is checked against it from then on.

FAQ

Questions about validate_migration

What does the validate_migration tool do? +

validate_migration is a execute tool on the Supabase MCP Server - Self-Hosted Edition MCP server. 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 validate_migration? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for validate_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 validate_migration? +

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

Can I rate-limit validate_migration? +

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

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

validate_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.

KEEP EXPLORING

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

This server

All 57 Supabase MCP Server - Self-Hosted Edition tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →