# list_migrations

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

Agent View of the PolicyLayer registry record for `list_migrations`. HTML page: https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/list-migrations

## Facts

- Tool: `list_migrations`
- Server: Supabase MCP Server - Self-Hosted Edition (`abdqum/supabase-mcp-selfhosted`) — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted.md
- Homepage: https://github.com/abdqum/Supabase-MCP-SelfHosted
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_migrations",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Supabase MCP Server - Self-Hosted Edition:

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

## Other tools on Supabase MCP Server - Self-Hosted Edition (56)

- `delete_auth_user` — Destructive — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/delete-auth-user.md
- `delete_subscription` — Destructive — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/delete-subscription.md
- `apply_migration` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/apply-migration.md
- `auto_create_indexes` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/auto-create-indexes.md
- `auto_migrate` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/auto-migrate.md
- `execute_psql` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/execute-psql.md
- `execute_sql` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/execute-sql.md
- `manage_docker` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/manage-docker.md
- `manage_functions` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/manage-functions.md
- `manage_triggers` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/manage-triggers.md
- `push_migrations` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/push-migrations.md
- `realtime_management` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/realtime-management.md
- `rebuild_hooks` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/rebuild-hooks.md
- `smart_migration` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/smart-migration.md
- `sync_schema` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/sync-schema.md
- `vacuum_analyze` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/vacuum-analyze.md
- `validate_migration` — Execute — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/validate-migration.md
- `hello` — Other — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/hello.md
- `analyze_performance` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/analyze-performance.md
- `analyze_rls_coverage` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/analyze-rls-coverage.md
- `audit_security` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/audit-security.md
- `check_health` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/check-health.md
- `generate_typescript_types` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/generate-typescript-types.md
- `get_anon_key` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/get-anon-key.md
- `get_auth_user` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/get-auth-user.md
- `get_database_connections` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/get-database-connections.md
- `get_database_stats` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/get-database-stats.md
- `get_logs` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/get-logs.md
- `get_project_url` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/get-project-url.md
- `get_service_key` — Read — https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted/get-service-key.md
- …and 26 more: https://policylayer.com/tools/abdqum-supabase-mcp-selfhosted.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=abdqum-supabase-mcp-selfhosted · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abdqum-supabase-mcp-selfhosted
