db-rls-audit

Audit PostgreSQL tables for Row Level Security status and policies.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill db-rls-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-rls-audit
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/database/db-rls-audit
Command: npx skills add https://github.com/GDSDN/kord-aios --skill db-rls-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify and report on Row Level Security (RLS) status across your database tables, highlighting tables with missing RLS or incomplete policy coverage to prevent security vulnerabilities.

Core Features & Use Cases

  • RLS Status Reporting: Identifies tables with RLS enabled or disabled.
  • Policy Listing: Lists all defined RLS policies for each table.
  • Security Risk Identification: Flags tables that are at risk due to disabled RLS or missing policies.
  • Use Case: Before deploying a new feature that modifies database access, run this audit to ensure all sensitive tables have appropriate RLS policies in place, preventing accidental data exposure.

Quick Start

Run a comprehensive RLS audit on the database.

Frequently Asked Questions about db-rls-audit

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

FAQPage Schema
How do I audit PostgreSQL tables for Row Level Security status?

Auditing PostgreSQL tables for Row Level Security involves scanning the database to identify RLS status and list all associated policies. This identifies tables with disabled RLS or incomplete policy coverage to prevent accidental data exposure.

How can I find tables with missing RLS policies in my database?

Finding tables with missing RLS policies requires running an audit that flags tables with disabled RLS or incomplete policy coverage. This security risk identification highlights tables that are at risk due to missing policies before deploying new features.

What is the best way to check RLS policy coverage before a database deployment?

The best way to check RLS policy coverage before deployment is to run a comprehensive RLS audit. This reports RLS status and lists all defined policies for each table, ensuring sensitive tables have appropriate policies in place to prevent data exposure.

Can I automate reporting for disabled RLS tables in PostgreSQL?

Yes, you can automate reporting for disabled RLS tables in PostgreSQL. The audit supports automated reporting to identify tables with RLS enabled or disabled, allowing manual intervention for policy creation and RLS enforcement where needed.

Why does running an RLS audit help prevent data exposure?

Running an RLS audit helps prevent data exposure by identifying tables with disabled RLS or incomplete policy coverage. By flagging these security risks, you can enforce RLS and create policies to ensure all sensitive tables have appropriate access controls.