supabase-audit-rls

Name: supabase-audit-rls
Availability: InStock
Author: marvinbiss

Audit Supabase RLS policies for bypass vulnerabilities and misconfigurations.

Updated Jan 31, 2026

Search Tags:#security #vulnerability #rls #audit #supabase #data protection

Ready to run

npx skills add https://github.com/marvinbiss/servicesartisans --skill supabase-audit-rls-marvinbiss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supabase-audit-rls
Source: https://github.com/marvinbiss/servicesartisans/tree/main/.cursor/skills/supabase-audit-rls
Command: npx skills add https://github.com/marvinbiss/servicesartisans --skill supabase-audit-rls-marvinbiss

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies and helps fix critical Row Level Security (RLS) misconfigurations in Supabase, preventing unauthorized data access and exposure.

Core Features & Use Cases

RLS Policy Auditing: Automatically tests RLS policies for common bypass vulnerabilities like unauthenticated access, cross-user access, and filter bypasses.
Vulnerability Identification: Pinpoints tables with disabled RLS, missing policies, or overly permissive rules.
Use Case: After deploying new features that involve user data, run this audit to ensure that users can only access their own records and that sensitive information remains protected from external or unauthorized access.

Quick Start

Audit RLS policies on my Supabase project.

Frequently Asked Questions about supabase-audit-rls

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

FAQPage Schema

How do I audit Supabase Row Level Security policies for bypass vulnerabilities?▼

To audit Supabase Row Level Security policies, you need a tool that automatically tests tables for disabled RLS, missing policies, and overly permissive rules. This process detects unauthenticated access, cross-user access, filter bypasses, and join exploitation vectors.

What common RLS misconfigurations can expose my Supabase data to unauthorized access?▼

Common Supabase RLS misconfigurations include disabled RLS on tables, missing policies, and overly permissive rules. These vulnerabilities expose data to unauthenticated access, cross-user access, filter bypasses, and join exploitation.

Can I test for cross-user access and filter bypasses in my Supabase RLS setup?▼

Yes, you can test for cross-user access and filter bypasses by running an automated RLS audit. Supplying your Supabase project details and an authenticated user token enables comprehensive vulnerability testing against these specific bypass vectors.

Do I need an authenticated user token to run a comprehensive Supabase RLS audit?▼

You need Supabase project details to run an RLS audit, and an authenticated user token is optionally required. Providing the token allows the audit to perform comprehensive testing of policies against authenticated access scenarios and cross-user vulnerabilities.

When should I run an RLS audit on my Supabase database?▼

You should run an RLS audit after deploying new features that involve user data. This ensures that recently added tables or policies do not expose sensitive information through unauthenticated access or cross-user access vulnerabilities.

Does this RLS audit identify tables with disabled Row Level Security in Supabase?▼

Yes, the RLS audit identifies tables with disabled Row Level Security in Supabase. It also pinpoints missing policies and overly permissive rules to prevent unauthorized data access and exposure.