Low Risk

get_department_users

获取指定部门下的所有成员列表。当你需要了解某个部门有哪些成员,或者需要批量获取部门成员信息时使用此工具。

How to control get_department_users ↓

What get_department_users does on DingTalk MCP Server V2

AI agents call get_department_users 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.

Low Risk

Why get_department_users needs a policy

This tool retrieves organizational membership information from DingTalk without performing any writes, deletions, or external operations. It is a read-only query that lists users in a department.

From the tool's definition Tool name 'get_department_users' and description '获取指定部门下的所有成员列表' (retrieve all member list under specified department) indicate data retrieval with no modification or deletion.

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

How to control get_department_users

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_department_users:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_department_users": {}
  }
}

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

  1. Create a free account and register DingTalk MCP Server V2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_department_users

What does the get_department_users tool do? +

获取指定部门下的所有成员列表。当你需要了解某个部门有哪些成员,或者需要批量获取部门成员信息时使用此工具。. It is categorised as a Read tool in the DingTalk MCP Server V2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_department_users? +

Register the DingTalk MCP Server V2 MCP server in PolicyLayer and add a rule for get_department_users: 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.

What risk level is get_department_users? +

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

Can I rate-limit get_department_users? +

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

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

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

Enforce policy on every DingTalk MCP Server V2 tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.