High-risk tools in Supabase MCP Server - Self-Hosted Edition
15 of the 57 tools in Supabase MCP Server - Self-Hosted Edition are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
apply_migrationExecuteAdvanced migrations with validation
-
auto_create_indexesExecuteauto_create_indexes
-
auto_migrateExecuteauto_migrate
-
execute_psqlExecuteDirect PostgreSQL access
-
execute_sqlExecuteEnhanced SQL with OAuth2 DDL support
-
manage_dockerExecuteManage Docker containers for self-hosted Supabase (status, logs, restart)
-
manage_functionsExecutemanage_functions
-
manage_triggersExecutemanage_triggers
-
push_migrationsExecutepush_migrations
-
realtime_managementExecuteComprehensive Supabase Realtime management with channels, broadcasts, presence, and security controls
-
rebuild_hooksExecuterebuild_hooks
-
smart_migrationExecutesmart_migration
-
sync_schemaExecutesync_schema
-
vacuum_analyzeExecutevacuum_analyze
-
validate_migrationExecutevalidate_migration
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.