call_auth_admin_method

THE RISK

High Risk

Why call_auth_admin_method needs a policy

This tool executes arbitrary Auth Admin SDK methods, which can include creating, updating, or deleting users, managing sessions, and other privileged identity operations. The description is vague but 'calls a method' implies dynamic execution of SDK operations. Auth admin operations can be highly impactful (e.g., deleting users, revoking tokens), making severity high.

From the tool's definition 'Calls a method of the Python SDK client' — executes SDK methods against the Auth Admin API

Documented attack patterns abuse exactly the kind of access call_auth_admin_method gives an agent:

POLICY

How to control call_auth_admin_method

PolicyLayer is an MCP gateway — it sits between your AI agents and Supabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for call_auth_admin_method:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_auth_admin_method": {
      "limits": [
        {
          "counter": "call_auth_admin_method_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

call_auth_admin_method stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Supabase MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Supabase MCP Server tools

Execute execute_sql_query Execute an SQL query with validation. Execute live_dangerously Toggle between safe and unsafe operation modes for a specific service. Execute send_management_api_request send_management_api_request Read get_auth_admin_methods_spec Returns the Python SDK spec Read get_db_schemas List all database schemas with their sizes and table counts. Read get_management_api_safety_rules Get all safety rules for the Supabase Management API Read get_management_api_spec Get enriched API specification with safety information. Read get_table_schema Get detailed table structure including columns, keys, and relationships.

All 10 Supabase MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Supabase MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about call_auth_admin_method

What does the call_auth_admin_method tool do? +

Calls a method of the Python SDK client. It is categorised as a Execute tool in the Supabase MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on call_auth_admin_method? +

Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for call_auth_admin_method: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Supabase MCP Server. Nothing to install.

What risk level is call_auth_admin_method? +

call_auth_admin_method is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_auth_admin_method? +

Yes. Add a rate_limit block to the call_auth_admin_method rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block call_auth_admin_method completely? +

Set action: deny in the PolicyLayer policy for call_auth_admin_method. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides call_auth_admin_method? +

call_auth_admin_method is provided by the Supabase MCP Server MCP server (deploya-labs/mcp-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Supabase MCP Server tool call.

Start from Supabase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →