Get a specific user by ID
AI agents call supabase_get_user to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from the Supabase database without modifying, deleting, or executing any operations. It is a simple read query that returns data about a user. The operation is non-destructive and has minimal security risk if misused (potential information disclosure, but only of already-stored user metadata). Low severity reflects the limited blast radius of unintended usage.
From the tool's definition Tool name is 'supabase_get_user' and description states 'Get a specific user by ID' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a specific user by ID. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server 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 Supabase MCP Server. Nothing to install.
supabase_get_user 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 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.
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.
supabase_get_user is provided by the Supabase MCP Server MCP server (sweir1/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →