// SCAN REPORT

Supabase MCP Server - Self-Hosted Edition

57 tools. 34 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 16 Aug 2026

34 can modify or destroy data

23 read-only

57 tools total

Community server · catalogue entry checked 16/08/2026

How to control Supabase MCP Server - Self-Hosted Edition ↓

TOOL MAP

What Supabase MCP Server - Self-Hosted Edition exposes to your agents

Read (23) Write / Execute (31) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Supabase MCP Server - Self-Hosted Edition tools

Destructive · High delete_auth_user User deletion is a destructive operation that cannot be undone without restore from backup. Destructive · High delete_subscription The 'delete' prefix categorizes this as Destructive rather than Write, as subscriptions typically cannot be easily recreated with identical state and history. Execute · Critical execute_psql This tool provides direct access to execute arbitrary PostgreSQL queries and commands. Execute · Critical execute_sql This tool executes SQL queries with DDL support on a Supabase database instance.

34 of Supabase MCP Server - Self-Hosted Edition's 57 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Supabase MCP Server - Self-Hosted Edition

PolicyLayer is an MCP gateway — it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_auth_user": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "backup_database": {
    "limits": [
      {
        "counter": "backup_database_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_performance": {
    "limits": [
      {
        "counter": "analyze_performance_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Supabase MCP Server - Self-Hosted Edition — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SUPABASE MCP SERVER - SELF-HOSTED EDITION →

Instant setup, no code required.

FULL CATALOGUE

All 57 Supabase MCP Server - Self-Hosted Edition tools

DESTRUCTIVE 2 tools

Destructive delete_auth_user delete_auth_user Destructive delete_subscription delete_subscription

EXECUTE 15 tools

Execute apply_migration Advanced migrations with validation Execute auto_create_indexes auto_create_indexes Execute auto_migrate auto_migrate Execute execute_psql Direct PostgreSQL access Execute execute_sql Enhanced SQL with OAuth2 DDL support Execute manage_docker Manage Docker containers for self-hosted Supabase (status, logs, restart) Execute manage_functions manage_functions Execute manage_triggers manage_triggers Execute push_migrations push_migrations Execute realtime_management Comprehensive Supabase Realtime management with channels, broadcasts, presence, and security controls Execute rebuild_hooks rebuild_hooks Execute smart_migration smart_migration Execute sync_schema sync_schema Execute vacuum_analyze vacuum_analyze Execute validate_migration validate_migration

WRITE 16 tools

Write backup_database Create a backup of the PostgreSQL database with various options Write cache_management cache_management Write create_auth_user create_auth_user Write create_migration create_migration Write create_subscription create_subscription Write environment_management environment_management Write generate_crud_api generate_crud_api Write import_schema Import OAuth2 schemas with extensions Write manage_extensions manage_extensions Write manage_realtime manage_realtime Write manage_rls_policies manage_rls_policies Write manage_roles manage_roles Write manage_secrets manage_secrets Write manage_storage_policies manage_storage_policies Write manage_webhooks manage_webhooks Write update_auth_user update_auth_user

READ 23 tools

Read analyze_performance analyze_performance Read analyze_rls_coverage analyze_rls_coverage Read audit_security audit_security Read check_health check_health Read generate_typescript_types generate_typescript_types Read get_anon_key get_anon_key Read get_auth_user get_auth_user Read get_database_connections get_database_connections Read get_database_stats get_database_stats Read get_logs get_logs Read get_project_url get_project_url Read get_service_key get_service_key Read inspect_schema Schema inspection with TypeScript Read list_auth_users list_auth_users Read list_extensions list_extensions Read list_migrations list_migrations Read list_realtime_publications list_realtime_publications Read list_storage_buckets list_storage_buckets Read list_storage_objects list_storage_objects Read list_tables list_tables Read metrics_dashboard metrics_dashboard Read search_docs search_docs Read verify_jwt_secret verify_jwt_secret

OTHER 1 tools

Other hello Hello World

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Supabase MCP Server - Self-Hosted Edition

Can an AI agent delete data through the Supabase MCP Server - Self-Hosted Edition MCP server? +

Yes. The Supabase MCP Server - Self-Hosted Edition server exposes 2 destructive tools including delete_auth_user, delete_subscription. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Supabase MCP Server - Self-Hosted Edition? +

The Supabase MCP Server - Self-Hosted Edition server has 16 write tools including backup_database, cache_management, create_auth_user. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Supabase MCP Server - Self-Hosted Edition.

How many tools does the Supabase MCP Server - Self-Hosted Edition MCP server expose? +

57 tools across 4 categories: Destructive, Execute, Read, Write. 23 are read-only. 34 can modify, create, or delete data.

How do I enforce a policy on Supabase MCP Server - Self-Hosted Edition? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Supabase MCP Server - Self-Hosted Edition tool call.

Deterministic rules across all 57 Supabase MCP Server - Self-Hosted Edition tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SUPABASE MCP SERVER - SELF-HOSTED EDITION →

Instant setup, no code required.

57 Supabase MCP Server - Self-Hosted Edition tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Supabase MCP Server - Self-Hosted Edition's registry record.

The record behind this page: 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 →