Search Psychevus

12 results available.
↑ ↓ to navigate ↵ to open · esc to close

Free tool · Supabase

Your RLS is on. Can a stranger still read your tables?

Paste your schema and this simulates three people against every table: a stranger holding the public key from your JavaScript, someone who signed up five minutes ago, and the row’s real owner. You see who can read, create, change and delete, why, and the exact fix.

Runs in your browser. Your schema is never uploaded, and no data is needed: only table, policy, view and function definitions.

What it catches

Beyond “RLS enabled”.

Questions

Good to know.

How is this different from checking that RLS is enabled?

A table can have RLS enabled and still be fully readable: one permissive policy with using (true) lets everyone it applies to see every row, because policies are OR-ed. This tool evaluates the policies the way PostgreSQL combines them and tells you who actually gets in.

Is my schema uploaded?

No. The analysis runs in your browser and nothing is sent. It only needs definitions (tables, policies, views, functions), never data. AI assistants and scripts can use the same engine through the API or the MCP tool analyze_supabase_rls.

Where do I get my schema?

Run supabase db dump -f schema.sql with the Supabase CLI, paste your migrations, or copy the export query from this page into the SQL editor and paste its single result cell.

Can a clean result prove my app is safe?

No. It shows your policies don't open tables to strangers or to every user, under the assumptions listed with the result. Edge Functions, server code, storage and service-role usage can still expose data. That is what the Launch Check tests, with two real accounts.

Guides

Fix it properly.

YOUR VISIT, YOUR CHOICE

Privacy, by intention.

You decide what stays on your device. You can change your choice at any time.

Essential

Saves your privacy choice. Administrator sign-in uses a secure session cookie.

Always on
Full privacy notice ↗