update_auth_user

A write tool on the Supabase MCP Server - Self-Hosted Edition MCP server.

SERVERSupabase MCP Server - Self-Hosted Edition SOURCEabdqum/supabase-mcp-selfhosted

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/update-auth-user.md

WHAT IT DOES

What update_auth_user does on Supabase MCP Server - Self-Hosted Edition

AI agents use update_auth_user to create or update resources in Supabase MCP Server - Self-Hosted Edition, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase MCP Server - Self-Hosted Edition environment.

RISK

Why update_auth_user is rated Medium

This tool creates or modifies user authentication records reversibly (passwords, email, profile data can be changed again), placing it in the Write category. Severity is high because unauthorized modification of authentication credentials or user accounts could grant attackers access to systems or compromise user identities, affecting multiple users depending on agent context.

From the tool's definition Tool name 'update_auth_user' indicates modification of authentication user records. Server context shows this is a Supabase authentication management tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_auth_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_auth_user, this is the rule to start with:

update_auth_user Rate-limited

update_auth_user stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_auth_user": {
      "limits": [
        {
          "counter": "update_auth_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every update_auth_user call is checked against it from then on.

FAQ

Questions about update_auth_user

What does the update_auth_user tool do? +

update_auth_user is a write tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Write tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_auth_user? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for update_auth_user: 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 - Self-Hosted Edition. Nothing to install.

What risk level is update_auth_user? +

update_auth_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_auth_user? +

Yes. Add a rate_limit block to the update_auth_user 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 update_auth_user completely? +

Set action: deny in the PolicyLayer policy for update_auth_user. 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 update_auth_user? +

update_auth_user is provided by the Supabase MCP Server - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.

This server

All 57 Supabase MCP Server - Self-Hosted Edition tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →