根据用户姓名查询用户的详细信息。当你只知道用户的姓名，需要获取该用户的其他信息（如 userid、手机号、邮箱等）时使用此工具。
AI agents call find_user_by_name to retrieve information from DingTalk MCP Server V2 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 based on a name query. It performs a lookup operation returning data like userid, phone, and email without modifying or deleting any data. This is a straightforward Read operation.
From the tool's definition Tool name 'find_user_by_name' and description indicating it queries user details by name: '根据用户姓名查询用户的详细信息' (query user detailed information by user name).
Documented attack patterns abuse exactly the kind of access find_user_by_name gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DingTalk MCP Server V2, and nothing reaches the server without passing your rules. This is the rule we recommend for find_user_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"find_user_by_name": {}
}
}find_user_by_name is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
根据用户姓名查询用户的详细信息。当你只知道用户的姓名，需要获取该用户的其他信息（如 userid、手机号、邮箱等）时使用此工具。. It is categorised as a Read tool in the DingTalk MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the DingTalk MCP Server V2 MCP server in PolicyLayer and add a rule for find_user_by_name: 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 DingTalk MCP Server V2. Nothing to install.
find_user_by_name 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 find_user_by_name 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 find_user_by_name. 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.
find_user_by_name is provided by the DingTalk MCP Server V2 MCP server (wllcnm/dingding_mcp_v2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DingTalk MCP Server V2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 DingTalk MCP Server V2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.