AI agents call list_repository_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 |
|---|---|---|---|
accessLevel | number | — | Minimum access level: 20, 30, or 40. |
repositoryId | string | Yes | Repository ID (numeric ID or full path like org/repo). Use list_repositories to find the repository ID. |
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 repository member information for discovery purposes. It is a read-only operation that retrieves existing data without creating, modifying, deleting, or executing any operations. The stated use case (discovering user IDs for assignment or review) confirms it is informational lookup only.
From the tool's definition Tool name 'list_repository_members' and description explicitly states 'List members' and 'discover user IDs' — purely retrieves/queries data with no side effects.
Attacks that exploit this kind of access
List members who have access to a CodeUp repository. Use this to discover user IDs for assignment or review. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_repository_members accepts 3 parameters: accessLevel, repositoryId, organizationId. Required: repositoryId. 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_repository_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_repository_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_repository_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_repository_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_repository_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 →