New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_auth_user

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

SERVERSupabase MCP Server - Self-Hosted Edition SOURCEabdqum/supabase-mcp-selfhosted
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

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

AI agents call delete_auth_user to permanently remove resources in Supabase MCP Server - Self-Hosted Edition, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_auth_user is rated Critical

User deletion is a destructive operation that cannot be undone without restore from backup. Even though the description is empty, the tool name unambiguously indicates irreversible data removal. This ranks as Destructive rather than Write due to the permanent nature of account deletion.

From the tool's definition Tool name is 'delete_auth_user' with no description provided. The name explicitly indicates deletion of authentication user records, which is irreversible.

Questions about delete_auth_user

What does the delete_auth_user tool do? +

delete_auth_user is a destructive tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Destructive tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_auth_user? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for delete_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 delete_auth_user? +

delete_auth_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_auth_user? +

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

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

delete_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Supabase MCP Server - Self-Hosted Edition's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.