Connect Supabase to enable agents to:
- Audit RLS policies for tables referenced in PR changes
- Generate SQL migrations to remediate missing or unsafe policies
- Commit fixes for Critical / High / Medium issues to the PR branch
- Post (or update) a single PR comment with scope, findings, and changes
Official Workflow Templates
The following official workflow template is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Supabase security reviews.Supabase security review
When a pull request is opened, automatically audits RLS for tables referenced in that PR, commits fixes for Critical/High/Medium issues, and posts (or updates) a single PR comment with results.
Risk Levels Explained
🔴 Critical — Immediate fix required
🔴 Critical — Immediate fix required
Tables with sensitive data that have no RLS enabled.Examples
- User profiles or authentication-related tables
- Financial or billing data
- Private messages or personal content
- RLS is enabled automatically
- Baseline access policies are generated
- Fixes are committed directly to the PR branch
🟠 High — Serious security gap
🟠 High — Serious security gap
Policies exist but are overly permissive or unsafe.Examples
- Policies using
USING (true) - Write access without proper ownership checks
- Admin policies without role validation
- Restrictive policies are generated
- Unsafe rules are replaced
- Fixes are committed to the PR branch
🟡 Medium — Missing best practices
🟡 Medium — Missing best practices
Partial or incomplete RLS coverage.Examples
- SELECT policy exists but UPDATE or DELETE is missing
- Missing user-scoped access patterns
- Incomplete CRUD coverage
- Missing policies are added
- Fixes are committed to the PR branch
🟢 Low — Optimization opportunity
🟢 Low — Optimization opportunity
Policies work, but could be improved.Examples
- Poor policy naming
- Redundant or inefficient rules
- Missing documentation
- No automatic fixes
- Suggestions are included in the PR comment only
Advanced Use Cases
Advanced: Custom Supabase Workflow Ideas
Advanced: Custom Supabase Workflow Ideas
These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows.
- Run scheduled audits across high-risk tables (beyond PR scope)
- Generate migration suggestions for schema changes even when no issues are Critical/High/Medium
- Review SQL performance risks (missing indexes, expensive queries) before merge
- Enforce schema conventions (naming, constraints, standard columns)
- Generate “security notes” summaries for release PRs or weekly reports
Access & Permissions
When connecting Supabase, you’ll authorize Continue to access your Supabase project(s) through the integration.-
Project selection
Choose the Supabase organization and project you want Mission Control to connect to. -
Permissions
Approved permissions allow Continue to inspect RLS and policies, generate recommended migrations, and support workflows that comment on PRs and commit fixes.