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

get_auth_user

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

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

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

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

AI agents call get_auth_user to retrieve information from Supabase MCP Server - Self-Hosted Edition without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_auth_user is rated Low

This tool retrieves user authentication information without modifying it. While the description is empty (lowering confidence slightly), the naming convention and position among authentication tools strongly indicate a read operation.

From the tool's definition Tool name 'get_auth_user' indicates retrieval of authentication user data. Context shows this is part of a Supabase authentication management suite.

Questions about get_auth_user

What does the get_auth_user tool do? +

get_auth_user is a read tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Read tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_auth_user? +

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

get_auth_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_auth_user? +

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

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

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