audit-rls

Audit PostgreSQL tables for missing or misconfigured Row-Level Security policies.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/SomtechSolutionMAxime/somtech-pack --skill audit-rls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-rls
Source: https://github.com/SomtechSolutionMAxime/somtech-pack/tree/main/.claude/skills/audit-rls
Command: npx skills add https://github.com/SomtechSolutionMAxime/somtech-pack --skill audit-rls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing Row-Level Security policies to ensure correct data access controls across tables and schemas.

Core Features & Use Cases

  • Quickly identify tables lacking RLS
  • Validate policies for correct USING and WITH CHECK configurations
  • Generate a compliance report to support security audits
  • Use case: multi-tenant databases requiring policy coverage checks

Quick Start

Run a targeted RLS audit against your PostgreSQL project to produce a compliance report.

Frequently Asked Questions about audit-rls

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

FAQPage Schema
How do I audit Row-Level Security policies in PostgreSQL?

To audit Row-Level Security policies in PostgreSQL, you can inspect database tables to identify missing RLS configurations and validate existing policies for correct data access controls.

How do I find tables missing RLS policies in a multi-tenant database?

You can find tables missing RLS policies by running targeted SQL queries that inspect your PostgreSQL schemas, auditing multi-tenant tables to ensure complete policy coverage and correct data access controls.

What does checking USING and WITH CHECK configurations do for RLS validation?

Checking USING and WITH CHECK configurations validates that your Row-Level Security policies correctly restrict data access and enforce constraints during database operations.

Can I generate a compliance report for PostgreSQL RLS policies?

Yes, you can generate a compliance report for PostgreSQL RLS policies that documents policy validation results, index checks, and missing security configurations to support security audits.

Does this RLS audit work with PostgreSQL projects with multiple schemas?

Yes, this RLS audit works with PostgreSQL projects containing multiple schemas and tenants, inspecting tables across the database to verify policy coverage and identify misconfigured RLS policies.

Why are my Row-Level Security policies not restricting data access correctly?

Your Row-Level Security policies may be misconfigured, lacking proper USING or WITH CHECK clauses, or tables may be missing RLS entirely, allowing incorrect data access across schemas.