Get workload trend analysis for project members including current task counts, status distribution, recent activity, and overdue items. Useful for capacity planning and identifying overloaded team members.
AI agents call get_member_workload_trend 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 |
|---|---|---|---|
daysBack | number | — | Number of days to look back for recent activity. Defaults to 30. |
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
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 analyze 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 retrieves and queries workload data for analysis purposes only. It has no side effects on data; it does not create, modify, delete, or execute any operations. The stated use case of 'capacity planning and identifying overloaded team members' confirms it is a read-only analytics tool. Confidence is high because the description explicitly indicates data retrieval with no mutation.
From the tool's definition Tool description states it 'Get[s] workload trend analysis' and provides 'current task counts, status distribution, recent activity, and overdue items' — purely informational retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get workload trend analysis for project members including current task counts, status distribution, recent activity, and overdue items. Useful for capacity planning and identifying overloaded team members. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_member_workload_trend accepts 6 parameters: daysBack, projectId, 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_member_workload_trend: 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_member_workload_trend 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_member_workload_trend 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_member_workload_trend. 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_member_workload_trend 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 →