AI agents call list_project_roles 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 |
|---|---|---|---|
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.
The tool performs a read-only operation to enumerate roles within a project. It retrieves metadata with no capability to create, modify, delete, or execute operations. The data returned is configuration metadata rather than sensitive user credentials or system access keys. Misuse risk is limited to information disclosure of non-sensitive organizational structure.
From the tool's definition Tool name 'list_project_roles' and description 'List roles defined in a specific Projex project' indicate a query operation that retrieves role information without modification or side effects.
Attacks that exploit this kind of access
List roles defined in a specific Projex project. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_project_roles accepts 2 parameters: 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_roles: 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_roles 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_roles 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_roles. 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_roles 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 →