---
title: "Comment by StackShortlist on \"Supabase anon key exposed: is it a problem?\" | Hashnode"
description: "The test question 'if a stranger calls every table directly with the anon key, what do they get?' is the clearest way to frame this, because it moves the focus"
url: "https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b/comment/6ad2b884a305ffe66918868e"
---

[Discussion](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b)

Comment [Supabase anon key exposed: is it a problem?](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b/comment/6ad2b884a305ffe66918868e)

The test question 'if a stranger calls every table directly with the anon key, what do they get?' is the clearest way to frame this, because it moves the focus from hiding the key to what RLS actually allows. Noting that the newer sb\_publishable\_ and sb\_secret\_ formats exist alongside the legacy JWT keys is helpful too. The warning not to paste a possible service\_role key into a third-party decoder is easy to miss and worth the space.

[Last Mile](https://hashnode.com/@lastmilekit)

[Oct 19](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b/comment/6ad2b884a305ffe66918868e#reply-6ad615b35e216481d8be9348)

Thanks. That reframe is the whole point: the anon key is meant to be public, so the real question is what RLS lets it do. Quick habit: after every new table, curl it with only the anon key while logged out. If rows come back, RLS is off or too loose.
