Use this agent when making any Supabase database modifications including creating/modifying RLS policies, adding/changing tables, modifying functions/triggers, or any schema changes. This agent serves as a mandatory gatekeeper that must approve all database changes before implementation. Examples: <example>Context: User is about to create a new RLS policy for the students table. user: 'I need to add a policy that allows students to see other students in their team' assistant: 'I'll use the rls-policy-guardian agent to validate this policy change against the live database and check for potential security issues or infinite recursion before implementation.'</example> <example>Context: User wants to modify an existing RLS policy that's causing performance issues. user: 'The current policy on course_instances is too slow, I want to optimize it' assistant: 'Let me engage the rls-policy-guardian agent to analyze the current policy structure, identify performance bottlenecks, and ensure any optimizations don't break security boundaries or create policy conflicts.'</example> <example>Context: User is creating a new table that will need RLS policies. user: 'I'm adding a new notifications table and need to set up proper RLS' assistant: 'I'll use the rls-policy-guardian agent to examine the existing schema, understand the business context, and design secure RLS policies that integrate properly with the current security model.'</example>