More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Supabase RLS Check

    1

    Check Supabase migrations before you push: public tables without row level security, policies that let anyone write, views that bypass RLS, policies that trust user_metadata, and service_role keys in SQL.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Supabase RLS Check

    Supabase RLS Check

    Example session with this skill installed

    Check this project with supabase-rls-check.

    • Read your context and instructions
    • Compiled the supabase rls check

    $ python3 scripts/check_supabase.py examples/risky
    BLOCK supabase/migrations/20240101000000_init.sql:4 R01 RLS_NOT_ENABLED
    create table public.profiles (
    Why: A table in the public schema has no row level security (or it is turned off). Supabase serves public tables through its API, so anyone with your anon key, which ships in your app, can read, change and delete every row.
    Safer: Run alter table <name> enable row level security; in the same migration, then add policies for the rows each user may see and change.

    BLOCK supabase/migrations/20240101000000_init.sql:17 R02 WRITE_OPEN_TO_EVERYONE
    BLOCK supabase/migrations/20240101000000_init.sql:26 R04 POLICY_TRUSTS_USER_METADATA
    BLOCK supabase/migrations/20240101000000_init.sql:29 R03 VIEW_BYPASSES_RLS
    BLOCK supabase/migrations/20240102000000_webhook.sql:4 R05 SERVICE_KEY_IN_SQL
    REVIEW supabase/migrations/20240101000000_init.sql:2 R14 EXTENSION_IN_PUBLIC
    REVIEW supabase/migrations/20240101000000_init.sql:20 R11 PUBLIC_READ
    REVIEW supabase/migrations/20240101000000_init.sql:23 R12 ANY_SIGNED_IN_USER_CAN_WRITE
    REVIEW supabase/migrations/20240101000000_init.sql:32 R13 SECURITY_DEFINER_FUNCTION_IN_API

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 2 files, 2 with Supabase SQL content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A table in Supabase's public schema without row level security can be read and changed by anyone who has your anon key, and that key ships inside your app. This skill finds that and eight other Supabase SQL mistakes, and tells you how to fix each one.

    Your agent runs a scanner on your supabase/migrations and schema files, in order, the way migrations run. RLS turned on in a later migration counts, renamed tables are followed, and supabase db pull output is understood. It reads policies (for, to, using, with check), views, security definer functions and extensions. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Keys are never printed.

    What it checks

    BLOCK

    • R01: a public table without row level security
    • R02: an insert, update or delete policy open to anon or public with true
    • R03: a public view without security_invoker, which bypasses RLS
    • R04: a policy that trusts user_metadata, which users can edit themselves
    • R05: a service_role key or sb_secret_ key written in SQL

    REVIEW

    • R11: a select policy open to everyone
    • R12: a write policy where any signed-in user can change any row
    • R13: a security definer function callable through the API
    • R14: an extension installed in the public schema

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • Risky and safe example migrations, and the real report the scanner produces on the risky ones

    Limits It reads SQL files, not your live database, so changes made in the dashboard are not seen. Run the Supabase Security Advisor too. NOT FLAGGED is not a guarantee.

    Static check of SQL text. Dashboard changes, grants and policies outside the scanned files are not seen; policies that call helper functions count as checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Requires

    python3 (3.9 or newer)

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example migration includes a clearly fake, inert key (sb_secret_not_a_real_key_0000) for the scanner to find.

    Listed8 days ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads your .sql files as text. It never connects to a database, runs SQL or needs your keys.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, risky and safe example migrations, and the real report the scanner prints on the risky example.

    New in Data & Databases