获取指定用户的详细信息。当你已经知道用户的 userid，需要获取该用户的详细信息时使用此工具。
AI agents call get_user_detail 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 from DingTalk given a userid parameter. It is fundamentally a query operation with no side effects. Severity is medium rather than low because user detail information may include sensitive personal or organizational data that could be misused if exposed to unauthorized agents, but the tool itself performs only read operations without affecting system state or data integrity.
From the tool's definition Tool name 'get_user_detail' and description indicate retrieval of user details: '获取指定用户的详细信息' (retrieve specified user's detailed information). No modification, deletion, or execution of external operations is implied.
Documented attack patterns abuse exactly the kind of access get_user_detail 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 get_user_detail:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_detail": {}
}
}get_user_detail 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 get_user_detail: 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.
get_user_detail 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 get_user_detail 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 get_user_detail. 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.
get_user_detail 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.