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

supabase_delete_user

Delete an auth user from the Supabase project.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp
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/shriram-vasudevan-integrations-mcp/supabase-delete-user.md

What supabase_delete_user does on Integrations MCP

AI agents call supabase_delete_user to permanently remove resources in Integrations MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why supabase_delete_user is rated Critical

This tool permanently removes user authentication data from a Supabase project, which cannot be undone and represents loss of a user account. This is a destructive operation with significant blast radius if triggered incorrectly by an AI agent (e.g., deleting the wrong user). While not financial in nature, destructive operations rank above execute/write/read in severity.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an auth user from the Supabase project' — this is an irreversible removal of user authentication records.

Questions about supabase_delete_user

What does the supabase_delete_user tool do? +

Delete an auth user from the Supabase project. It is categorised as a Destructive tool in the Integrations MCP 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 supabase_delete_user? +

Register the Integrations MCP server in PolicyLayer and add a rule for supabase_delete_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 Integrations MCP. Nothing to install.

What risk level is supabase_delete_user? +

supabase_delete_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 supabase_delete_user? +

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

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

supabase_delete_user is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Integrations, 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 Integrations'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.