search_user_in_supabase

THE RISK

Low Risk

Why search_user_in_supabase needs a policy

This tool queries a database to retrieve user information (ID and calendar ID) without modifying, deleting, or executing external operations. It is a standard read operation with minimal blast radius—exposure could leak user identifiers but does not enable destructive or financial actions.

From the tool's definition Tool description states 'Search for a user in Supabase database by partial name and get their user ID and calendar ID' — a retrieval operation with no side effects. The verb 'search' and 'get' indicate read-only queries returning user metadata.

Documented attack patterns abuse exactly the kind of access search_user_in_supabase gives an agent:

POLICY

How to control search_user_in_supabase

PolicyLayer is an MCP gateway — it sits between your AI agents and Lark MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_user_in_supabase:

policy.json

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

search_user_in_supabase is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Lark MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Lark MCP Server tools

Write add_attendees Add attendees to a calendar event on Lark Write create_event Create a calendar event on Lark Write send_message_to_user Send a message to the user on Lark Read list_events List events from the user on Lark

All 5 Lark MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_user_in_supabase

What does the search_user_in_supabase tool do? +

Search for a user in Supabase database by partial name and get their user ID and calendar ID. It is categorised as a Read tool in the Lark MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_user_in_supabase? +

Register the Lark MCP Server MCP server in PolicyLayer and add a rule for search_user_in_supabase: 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 Lark MCP Server. Nothing to install.

What risk level is search_user_in_supabase? +

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

Can I rate-limit search_user_in_supabase? +

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

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

search_user_in_supabase is provided by the Lark MCP Server MCP server (junyuan-qi/lark-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Lark MCP Server tool call.

Start from Lark MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →