AI agents call get_project_member_task_status 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 |
|---|---|---|---|
tag | string | — | Comma-separated tag IDs applied to every section. |
sprint | string | — | Comma-separated sprint IDs applied to every section. |
status | string | — | Comma-separated status IDs applied to assigned and overdue sections. |
creator | string | — | Comma-separated creator user IDs applied to every section. |
subject | string | — | Subject contains filter applied to every section. |
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
assignedTo | string | — | Comma-separated assignee user IDs applied to every section. |
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. |
sampleLimit | number | — | Samples returned per member section. Defaults to 5, clamped to 0-200. |
statusStage | string | — | Comma-separated status stage IDs applied to assigned and overdue sections. |
Parameters from the server's own tool schema.
This tool queries and retrieves existing task status data for team members within a project. The stated use case—workload balancing and identifying blocked team members—confirms it is a read-only operation that gathers information without side effects. No data is created, modified, deleted, or executed. Blast radius is minimal as misuse would only expose task visibility information.
From the tool's definition Tool name is 'get_project_member_task_status' with verb 'get'. Description explicitly states it retrieves 'per-member task status' for workload analysis. No modification, deletion, or execution of external operations mentioned.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Get per-member task status for one project with assigned, overdue, and optional status-group sections. Useful for workload balancing and identifying blocked team members. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_project_member_task_status accepts 12 parameters: tag, sprint, status, creator, subject, projectId, assignedTo, categories, assigneeIds, memberLimit, sampleLimit, statusStage. 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_project_member_task_status: 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_project_member_task_status 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_project_member_task_status 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_project_member_task_status. 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_project_member_task_status 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 →