create_auth_user
A write tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/create-auth-user.md
What create_auth_user does on Supabase MCP Server - Self-Hosted Edition
AI agents use create_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.
Why create_auth_user is rated Medium
Creating authentication users is a reversible write operation—new users can be deleted or modified later. It modifies system state (user records in the authentication system) but does not destroy data irreversibly or execute arbitrary code.
From the tool's definition Tool name 'create_auth_user' indicates creation of authentication user accounts. Server context describes 'authentication' management capabilities. The 'create_' prefix explicitly signals a write/create operation.
Attacks that exploit this kind of access
The rule that runs create_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 create_auth_user, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every create_auth_user call is checked against it from then on.
Questions about create_auth_user
create_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.
Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for create_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.
create_auth_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.
Across the catalogue