Get detailed status change timeline for a work item including timestamps, duration in each status, and responsible users. Parses activity history to extract workflow bottlenecks. Useful for analyzing why a task is delayed.
AI agents call get_workitem_status_timeline 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 |
|---|---|---|---|
workitemId | string | Yes | Work item ID (numeric string). Find it via search_workitems. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
includeWorkitem | boolean | — | Whether to include basic work item info. Defaults to true. |
Parameters from the server's own tool schema.
This tool queries historical workflow data to extract timeline and status information. It performs data retrieval and analysis without side effects, making it a Read operation. The blast radius is low since it only accesses audit/history information that already exists in the system.
From the tool's definition Tool retrieves and parses existing activity history and status timeline data ('Get detailed status change timeline', 'Parses activity history'). No modification, execution, deletion, or financial operations are performed.
Attacks that exploit this kind of access
Get detailed status change timeline for a work item including timestamps, duration in each status, and responsible users. Parses activity history to extract workflow bottlenecks. Useful for analyzing why a task is delayed. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_workitem_status_timeline accepts 3 parameters: workitemId, organizationId, includeWorkitem. Required: workitemId. 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_workitem_status_timeline: 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_workitem_status_timeline 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_workitem_status_timeline 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_workitem_status_timeline. 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_workitem_status_timeline 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 →