AI agents call search_organization_members 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. |
query | string | — | Member search query. Matches username, display name, or email. |
deptIds | array | — | Department IDs to filter by. Use list_organization_departments to discover valid department IDs. |
perPage | number | — | Page size for pagination. Supports 1-100. |
roleIds | array | — | Role IDs to filter by. Use list_organization_roles to discover valid role IDs. |
statuses | array | — | Member statuses to filter by. Common values: enabled, disabled. |
nextToken | string | — | Pagination next token from a previous response. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
includeChildren | boolean | — | Whether to include members from child departments. Set to true for broader searches across the org tree. |
Parameters from the server's own tool schema.
This tool retrieves organizational member information based on filters. It has no side effects, does not execute operations, create resources, delete data, or commit financial actions. The blast radius of misuse is minimal — an agent could enumerate users but cannot modify, delete, or perform privileged actions. This is a standard Read operation querying organizational metadata.
From the tool's definition Tool description explicitly states 'Search members' and 'find specific users' — operations that retrieve/query data without modification. The stated purpose is for 'assignment or review purposes' (information gathering), not execution or data modification.
Attacks that exploit this kind of access
Search members in a Yunxiao organization with filters. Use this to find specific users by name, department, or role for assignment or review purposes. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
search_organization_members accepts 9 parameters: page, query, deptIds, perPage, roleIds, statuses, nextToken, organizationId, includeChildren. 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 search_organization_members: 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.
search_organization_members 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_organization_members 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_organization_members. 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_organization_members 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 →