Supabase
Build Supabase table and RPC tools that respect row-level security, so an agent inherits the policies you already wrote.
Run fh add supabase to install a compatible client and create a managed, fixed-table lookup tool and test. Preserve Row Level Security through end-user identity when required, and never expose the service-role key to model context.
Generate table/RPC-specific tools with schema validation, limits, redaction, and approval for mutations.
For Fabric runtime persistence, connect a server-side pg.Pool to Supabase's direct Postgres or
session-pooler URL and pass it to postgresPersistence(). Do not use the browser Supabase client or
service-role key in agent tools. Transaction-pooler compatibility depends on the connection mode;
the direct connection is the reference configuration for migrations and long-lived Node hosts.