AI agents call list_users to retrieve information from Yunxiao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
deptId | string | — | Department ID. Use list_organization_departments to discover valid IDs. |
filter | string | — | Fuzzy filter for username, login, email, or phone. |
status | string | — | User status filter. Common values: enabled, deleted. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
Parameters from the server's own tool schema.
This tool performs a read-only query to list user data and discover account information. The stated use cases (mentions, assignments, cross-org collaboration) are all informational in nature. There are no indications of data modification, deletion, execution of commands, or financial operations.
From the tool's definition Tool description explicitly states 'List Yunxiao users' and 'discover user IDs and account information' — retrieval operations with no side effects. No modifications, deletions, or external state changes are indicated.
Attacks that exploit this kind of access
List Yunxiao users across organizations. Use this to discover user IDs and account information for mentions, assignments, or cross-org collaboration. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_users accepts 5 parameters: page, deptId, filter, status, perPage. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for list_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 Yunxiao. Nothing to install.
list_users 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 list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_users is provided by the Yunxiao MCP server (@futuretea/yunxiao-mcp-server). 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 →