
Security checks for Next.js + Supabase apps: code scan, read-only live DB check, fix confirmation.
Public tool metadata for what this MCP can expose to an agent.
scan_filesStatic scan of the files your agent sends. Each finding comes with the fix.Static scan of the files your agent sends. Each finding comes with the fix.
No parameter schema in public metadata yet.
get_supabase_snapshot_sqlA read-only query for the project's catalog: table and column names, RLS flags, policies, grants, triggers, functions, bucket settings. Never rows.A read-only query for the project's catalog: table and column names, RLS flags, policies, grants, triggers, functions, bucket settings. Never rows.
No parameter schema in public metadata yet.
check_supabase_snapshotChecks the snapshot together with your Auth settings. With `previous_issue_keys` it reports what closed, what's new and what's still open.Checks the snapshot together with your Auth settings. With `previous_issue_keys` it reports what closed, what's new and what's still open.
No parameter schema in public metadata yet.
Sponsors
Security check for Next.js + Supabase apps, run by your AI agent. GuardLayer scans the code, checks the live Supabase project read-only, and after a fix confirms what actually closed.
It catches the holes AI-built apps usually ship with: tables anyone can read, RLS off, policies that only check for a signed-in user (public in practice when anyone can sign up), users who can change their own role or plan, service role keys in frontend code or NEXT_PUBLIC_ / VITE_ variables, and API routes, Server Actions and Edge Functions that don't check the caller.
claude plugin marketplace add solvionholdings/guardlayer-plugin
claude plugin install guardlayer@guardlayer
The plugin adds the GuardLayer MCP server and a skill that tells Claude when to use it: before a deploy, after changing tables or policies, or when it's about to loosen access to get past a permission error. Then ask: "Check this app for security issues with GuardLayer."