list_auth_users
A read tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/list-auth-users.md
What list_auth_users does on Supabase MCP Server - Self-Hosted Edition
AI agents call list_auth_users 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 list_auth_users is rated Low
This tool retrieves or queries user authentication records without modifying or deleting them, placing it in the Read category. Severity is medium rather than low because user data (especially auth records) is sensitive and could expose personally identifiable information or authentication credentials if misused by an agent, though the tool itself performs only read operations.
From the tool's definition Tool name 'list_auth_users' indicates retrieval of authentication user data; 'list' is a read operation pattern. Description is empty, lowering confidence slightly.
Attacks that exploit this kind of access
The rule that runs list_auth_users 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 list_auth_users, this is the rule to start with:
list_auth_users is read-only, so it stays allowed. 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 list_auth_users call is checked against it from then on.
Questions about list_auth_users
list_auth_users 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.
Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for list_auth_users: 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.
list_auth_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_auth_users 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 list_auth_users. 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.
list_auth_users 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