Searches for a user across all departments by their name.
AI agents call search_user_by_name to retrieve information from DingDing MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries user information across departments based on a name search parameter. It retrieves data with no side effects, no data modification, and no irreversible actions. The sibling tools (get_access_token, get_department_list, get_department_users) are similarly read-only.
From the tool's definition Tool name and description indicate retrieval functionality: 'Searches for a user... by their name.' Returns user information without modifying data.
Attacks that exploit this kind of access
Searches for a user across all departments by their name. It is categorised as a Read tool in the DingDing MCP MCP Server, which means it retrieves data without modifying state.
Register the DingDing MCP server in PolicyLayer and add a rule for search_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 DingDing MCP. Nothing to install.
search_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 search_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 search_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.
search_user_by_name is provided by the DingDing MCP server (wllcnm/dingding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →