AI agents call list_project_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 |
|---|---|---|---|
name | string | — | Filter by member name (contains match). |
roleId | string | — | Filter by project role ID, such as project.admin. Use list_project_roles to discover available roles. |
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool queries and returns information about project members without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves user/member data for informational purposes. Low severity due to limited blast radius if misused—it only exposes user IDs and member information within an authorized project context.
From the tool's definition Tool description states 'List members in a Projex project' and explains the purpose is to 'discover user IDs for filtering work items or assigning tasks'. This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List members in a Projex project. Use this to discover user IDs for filtering work items or assigning tasks. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_project_members accepts 4 parameters: name, roleId, projectId, organizationId. Required: projectId. 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_project_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.
list_project_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 list_project_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 list_project_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.
list_project_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 →