list_migrations

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

AI agents call list_migrations to retrieve information from Supabase MCP Server - Self-Hosted Edition without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_migrations is rated Low

The verb 'list' in database/migration contexts universally indicates a read-only query operation. The sibling tools include 'apply_migration' (Execute), 'auto_migrate' (Execute), and 'backup_database' (Read), confirming that distinct tools handle mutations. Absence of description lowers confidence slightly, but the semantic clarity of 'list' in this context is high. No side effects or data modifications are implied.

From the tool's definition Tool name 'list_migrations' indicates a retrieval/listing operation. No description provided, but the naming pattern and context within a database management server suggest it queries migration history rather than executing or modifying migrations.

The rule that runs list_migrations 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 list_migrations, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_migrations": {}
  }
}

Questions about list_migrations