// SCAN REPORT

DingTalk MCP Server V2

6 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 12 Jun 2026

0 can modify or destroy data

6 read-only

6 tools total

Community server · catalogue entry verified 12/06/2026

How to control DingTalk MCP Server V2 ↓

TOOL MAP

What DingTalk MCP Server V2 exposes to your agents

Read (6) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control DingTalk MCP Server V2

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. These are the rules we recommend:

Cap read operations

{
  "find_user_by_name": {
    "limits": [
      {
        "counter": "find_user_by_name_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register DingTalk MCP Server V2 — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DINGTALK MCP SERVER V2 →

Free to start. No card required.

FULL CATALOGUE

All 6 DingTalk MCP Server V2 tools

READ 6 tools

Read find_user_by_name 根据用户姓名查询用户的详细信息。当你只知道用户的姓名，需要获取该用户的其他信息（如 userid、手机号、邮箱等）时使用此工具。 Read get_access_token 获取钉钉 access_token。当你需要测试 API 连接状态，或者需要手动获取 access_token 时使用此工具。 Read get_calendar_list 查询指定用户的日程列表。当你需要查看用户的日程安排，或者需要了解会议室预订情况时使用此工具。 Read get_department_list 获取企业内所有部门的列表信息。当你需要了解公司的组织架构，或者需要获取某个部门的 ID 时使用此工具。 Read get_department_users 获取指定部门下的所有成员列表。当你需要了解某个部门有哪些成员，或者需要批量获取部门成员信息时使用此工具。 Read get_user_detail 获取指定用户的详细信息。当你已经知道用户的 userid，需要获取该用户的详细信息时使用此工具。

FAQ

Questions about DingTalk MCP Server V2

Is the DingTalk MCP Server V2 MCP server safe to use without restrictions? +

The DingTalk MCP Server V2 server is primarily read-only with 6 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the DingTalk MCP Server V2 MCP server expose? +

6 tools across 1 categories: Read. 6 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on DingTalk MCP Server V2? +

Register the DingTalk MCP Server V2 MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every DingTalk MCP Server V2 tool call.

Deterministic rules across all 6 DingTalk MCP Server V2 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DINGTALK MCP SERVER V2 →

Free to start. No card required.

6 DingTalk MCP Server V2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.