Get comprehensive details for a single work item including basic info, activities, attachments, comments, and relation records in one read-only call. Use this when you need the full picture of one specific work item.
AI agents call get_project_workitem_detail 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 |
|---|---|---|---|
page | number | — | Page number for comments. Defaults to 1. |
perPage | number | — | Page size for comments. Defaults to 20. |
workitemId | string | Yes | Work item ID (numeric string). Find it via search_workitems or get_project_workitem_summary. |
relationTypes | string | — | Comma-separated relation types for relation records. Defaults to ASSOCIATED,SUB. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
includeComments | boolean | — | Whether to include comments. Defaults to true. |
includeRelations | boolean | — | Whether to include relation records. Defaults to true. |
includeActivities | boolean | — | Whether to include activity history. Defaults to true. |
includeAttachments | boolean | — | Whether to include attachments. Defaults to true. |
Parameters from the server's own tool schema.
This tool performs a retrieval operation on work item data without side effects. The explicit 'read-only' designation and the verb 'Get' combined with the data retrieval purpose (fetching details, activities, attachments, comments, relations) clearly indicate a Read category classification. No destructive, financial, write, or execute operations are possible with this tool.
From the tool's definition Tool description explicitly states 'read-only call' and retrieves 'comprehensive details for a single work item including basic info, activities, attachments, comments, and relation records'. No modification, deletion, or execution capability is described.
Attacks that exploit this kind of access
Get comprehensive details for a single work item including basic info, activities, attachments, comments, and relation records in one read-only call. Use this when you need the full picture of one specific work item. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_project_workitem_detail accepts 9 parameters: page, perPage, workitemId, relationTypes, organizationId, includeComments, includeRelations, includeActivities, includeAttachments. 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_project_workitem_detail: 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_workitem_detail 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_workitem_detail 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_workitem_detail. 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_workitem_detail 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 →