get_findings
Audit Supabase/Postgres Row Level Security and return structured JSON findings grouped by severity, enabling agents to iterate findings, generate fixes, or build reports.
Instructions
Audit a Supabase/Postgres database's Row Level Security and return machine-readable structured JSON. Unlike audit_supabase_rls (which returns a human-readable summary), this tool returns findings grouped by severity with counts, suitable for programmatic consumption by an agent that needs to iterate over findings, generate fixes, or build a report. Same engine, same checks (tables, policies, Storage, SECURITY DEFINER functions, views, Realtime, default privileges, roles), different output shape. Each finding has kind, severity (fail/warn), object and detail; pass kind to explain_finding or generate_fix.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"db_url": "<db_url>"
},
"name": "get_findings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| allow | No | Policy names that are intentionally permissive. Prefer the qualified form "table.policy". | |
| db_url | Yes | Postgres connection string for the project to audit (e.g. postgresql://... — a read-only role is enough). | |
| schema | No | Schema to audit (default: public). | public |