Get a detailed per-member workload breakdown with current active tasks, task subjects, status, labels, and creation dates. Useful for stand-ups, sprint planning, and identifying what each team member is working on right now.
AI agents call get_team_workload_breakdown 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 |
|---|---|---|---|
status | string | — | Comma-separated status IDs to include. Defaults to all active statuses (backlog,待处理,处理中,测试中,In Review,pending). |
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
taskLimit | number | — | Max tasks returned per member. Defaults to 10, clamped to 1-50. |
categories | string | — | Comma-separated work item categories. Defaults to Task,Bug. |
assigneeIds | string | — | Comma-separated assignee user IDs. Defaults to project members up to memberLimit. |
memberLimit | number | — | Max project members to inspect when assigneeIds is omitted. Defaults to 20. |
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 retrieves team workload and task information for visibility purposes (stand-ups, sprint planning). It has no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an AI agent gaining access to this tool could only exfiltrate task metadata about team members, which is a low-severity information disclosure risk.
From the tool's definition Tool description states it 'Get[s] a detailed per-member workload breakdown' and retrieves 'current active tasks, task subjects, status, labels, and creation dates'.
Attacks that exploit this kind of access
Get a detailed per-member workload breakdown with current active tasks, task subjects, status, labels, and creation dates. Useful for stand-ups, sprint planning, and identifying what each team member is working on right now. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_team_workload_breakdown accepts 7 parameters: status, projectId, taskLimit, categories, assigneeIds, memberLimit, 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 get_team_workload_breakdown: 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.
get_team_workload_breakdown 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 get_team_workload_breakdown 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 get_team_workload_breakdown. 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.
get_team_workload_breakdown 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 →