Supabase Security

5 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated:

3 can modify or destroy data
2 read-only
5 tools total

Community server · catalogue entry verified 03/07/2026

How to control Supabase Security ↓

What Supabase Security exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (0)
High Risk

The most dangerous Supabase Security tools

3 of Supabase Security's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Supabase Security

PolicyLayer is an MCP gateway — it sits between your AI agents and Supabase Security, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "apply_all_fixes": {
    "limits": [
      {
        "counter": "apply_all_fixes_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "audit_project": {
    "limits": [
      {
        "counter": "audit_project_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Supabase Security — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON SUPABASE SECURITY →

Instant setup, no code required.

All 5 Supabase Security tools

Questions about Supabase Security

How do I prevent bulk modifications through Supabase Security? +

The Supabase Security server has 2 write tools including apply_all_fixes, preview_fix. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Supabase Security.

How many tools does the Supabase Security MCP server expose? +

5 tools across 2 categories: Read, Write. 2 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Supabase Security? +

Register the Supabase Security MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Supabase Security tool call.

Deterministic rules across all 5 Supabase Security tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

5 Supabase Security tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.