You can get most of the way there today without editing every existing policy, by adding one RESTRICTIVE policy per table. Permissive policies are OR'd together, but restrictive policies are AND'd with them, so a single extra policy can gate access no matter what the other policies say: ```sql create policy "Require aal2 for MFA-enrolled users" on public.your_table as restrictive to authenticated using ( array[(select auth.jwt()->>'aal')] <@ ( select case when count(id) > 0 then array['aal2'] else array['aal1', 'aal2'] end from auth.mfa_factors where (select auth.uid()) = user_id and status = 'verified' ) ); ``` This is the conditional version from the Supabase MFA docs: users with a verified factor need an `aal2` token, and users without one can still use `aal1`. If you want to require `aal2` for everyone, the body can be just `(select auth.jwt()->>'aal') = 'aal2'`. Because it is a separate policy, it also does not interfere with your existing permissive policies, and you can create it for every table in a loop over `pg_tables` in a migration. That addresses the "easy to miss on new tables" part a bit: you can add a check in CI that lists tables in `public` that have no restrictive aal2 policy. Two caveats: this only covers tables that go through RLS, so it does not protect Storage buckets (you would add the same kind of restrictive policy on `storage.objects`), `security definer` functions, or anything that uses the service role key. A gateway-level option would still be nicer, I agree.