- Home
- Skills
- Agents & Orchestration
- supabase rls policy auditor
Works with the AI Agents you already use
supabase rls policy auditor
Audit Supabase RLS policies for IDOR vulnerabilities and verify fixes with cross-tenant attack queries.
$22
supabase rls policy auditor
Example session with this skill installed
Audit my Supabase RLS policies for the 'orders' and 'profiles' tables. Here is my schema dump. Can a user see other people's orders?
- Read your context and instructions
- Compiled the supabase rls policy
Finding: 'orders' has RLS enabled but is missing a SELECT policy, defaulting to deny. 'profiles' has a permissive policy: 'Allow All' USING (true). This allows any authenticated user to read all profiles. I have generated a DROP POLICY and a hardened CREATE POLICY fix for you.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Supabase RLS policies often look correct while still leaking data due to permissive policy overlap or incorrect scoping columns. Relying on a visual audit of policy text is insufficient for identifying IDOR/BOLA vulnerabilities in a production database.
What it does
- Audits every table in a Supabase or Postgres project against an IDOR/BOLA attack matrix.
- Identifies missing RLS, overly permissive policies, and unsafe usage of user-editable JWT metadata.
- Generates precise remediation SQL including DROP, ALTER, and CREATE POLICY statements using hardened null-check patterns.
- Verifies fixes by generating and executing cross-tenant queries to prove enforcement rather than just reviewing code.
- Scans for service_role key leakage in client-side environment variables and source code.
Frameworks & tools
PostgreSQL, Supabase, and RLS (Row Level Security) mechanics.
Why this beats prompting it yourself
Generic LLMs often miss that Postgres combines permissive policies with OR, meaning adding a correct policy won't fix an existing leak. This skill enforces a "verify via query" workflow, ensuring you don't just feel safe, but are actually protected against cross-tenant access.
Use cases
- Reviewing Supabase-backed applications before moving from staging to production.
- Auditing legacy projects where RLS was applied inconsistently across different teams.
- Fixing data leaks where one table's policy inadvertently grants access to another tenant's rows.
- Validating that service_role keys are not exposed to the frontend or public mobile bundles.
Known limitations
Does not perform broad security audits like secrets scanning or logging. Verification queries require a connection that does not bypass RLS (non-superuser role).
Requires a non-superuser database role for meaningful verification. Not a general Postgres performance or schema design tool. Verification is limited to the provided schema scope.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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 2 months ago
Permissions
No special permissions declared or detected