supabase_get_user

Get details of a single auth user by ID.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

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/shriram-vasudevan-integrations-mcp/supabase-get-user.md

WHAT IT DOES

What supabase_get_user does on Integrations MCP

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

RISK

Why supabase_get_user is rated Low

This is a Read operation that queries user data from Supabase authentication. Severity is medium rather than low because it accesses sensitive personally identifiable information (PII) about users, including authentication details, which could be misused if an AI agent queries unauthorized user IDs. However, it has no destructive or side-effects capacity.

From the tool's definition Tool name and description: 'Get details of a single auth user by ID' — retrieves user authentication information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs supabase_get_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_get_user, this is the rule to start with:

supabase_get_user Allowed

supabase_get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "supabase_get_user": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every supabase_get_user call is checked against it from then on.

FAQ

Questions about supabase_get_user

What does the supabase_get_user tool do? +

Get details of a single auth user by ID. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on supabase_get_user? +

Register the Integrations MCP server in PolicyLayer and add a rule for supabase_get_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_get_user? +

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

Can I rate-limit supabase_get_user? +

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

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

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

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →