skills.rest
marvinbiss
marvinbissCOMMUNITY
Explore all skills by this author →
GitHub

supabase-audit-tables-read

Read Supabase tables to verify data exposure and RLS effectiveness.

Updated Jan 31, 2026
Search Tags:#security#database#rls#audit#supabase#data exposure
One-click install
npx skills add https://github.com/marvinbiss/servicesartisans --skill supabase-audit-tables-read-marvinbiss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supabase-audit-tables-read
Source: https://github.com/marvinbiss/servicesartisans/tree/main/.cursor/skills/supabase-audit-tables-read
Command: npx skills add https://github.com/marvinbiss/servicesartisans --skill supabase-audit-tables-read-marvinbiss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill verifies what data is actually accessible from your Supabase database tables, helping to identify potential data exposure and test Row Level Security (RLS) policies.

Core Features & Use Cases

  • Data Exposure Verification: Attempts to read data from tables to confirm what information is exposed.
  • RLS Policy Testing: Assesses the effectiveness of your RLS policies in preventing unauthorized access.
  • Severity Assessment: Classifies data exposure risks from critical (PII, secrets) to expected access.
  • Use Case: After listing your Supabase tables, use this Skill to perform read tests on sensitive tables like users or payments to ensure only authorized data is retrievable.

Quick Start

Test read access on all exposed tables using the quick mode.

Frequently Asked Questions about supabase-audit-tables-read

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify what data is exposed in my Supabase database tables?▼

You verify Supabase database data exposure by performing read tests on tables to confirm exactly what information is accessible, helping identify potential unauthorized access and classify risks from critical secrets to expected access.

What is needed to start auditing Supabase tables for data exposure risks?▼

To start auditing Supabase tables for data exposure risks, you need the Supabase anon key and a table listing from a prior audit step to perform read tests and verify RLS policy effectiveness.

Does this Supabase audit require a table listing before testing RLS policies?▼

Yes, Supabase RLS policy testing requires a table listing from a prior audit step and the Supabase anon key to attempt read operations and verify actual data exposure across the identified tables.

Why does my Supabase RLS policy still allow data reads from the anon key?▼

Supabase RLS policies may still allow data reads if the policy logic is misconfigured; auditing tables by attempting read operations with the anon key verifies actual data exposure and helps identify these security gaps.

Related Skills

Explore More Software Engineering Skills→
yoanbernabeuyoanbernabeu
62

supabase-audit-tables-list

Enumerate Supabase tables exposed via the PostgREST/OpenAPI schema.

Community
Basic
YanCheng-goYanCheng-go
3

security-review

Identify security risks across codebases, dependencies, secrets, and Supabase RLS policies.

Community
Advanced
gounthargounthar

supabase-expert

Provide Supabase guidance for database, auth, real-time, storage, and edge functions.

Community
Advanced
cwinvestmentscwinvestments
412

memstack-security-rls-checker

Audit Supabase Row Level Security policies across all tables.

Community
Intermediate