Get a Kanban-style board view of work items grouped by status for one project. Returns work items organized by their current status columns. For flat search results, use search_workitems instead.
AI agents call get_project_workitem_board 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 |
|---|---|---|---|
sprint | string | — | Optional sprint ID to filter work items. |
status | string | — | Comma-separated status IDs applied to the search. |
creator | string | — | Comma-separated creator user IDs applied to the search. |
subject | string | — | Subject contains filter applied to the search. |
category | string | Yes | Work item category, such as Task or Bug. |
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
assignedTo | string | — | Comma-separated assignee user IDs applied to the search. |
sampleLimit | number | — | Max work items returned. Defaults to 5, clamped to 0-200. |
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 project work item board data in a read-only manner. It has no side effects, does not modify data, execute commands, delete resources, or involve financial transactions. The action is informational only, similar to fetching or listing operations.
From the tool's definition Tool description states 'Get a Kanban-style board view' and 'Returns work items organized by their current status' — pure retrieval with no modification, creation, deletion, or external execution.
Attacks that exploit this kind of access
Get a Kanban-style board view of work items grouped by status for one project. Returns work items organized by their current status columns. For flat search results, use search_workitems instead. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_project_workitem_board accepts 9 parameters: sprint, status, creator, subject, category, projectId, assignedTo, sampleLimit, organizationId. Required: category, 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_workitem_board: 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_board 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_board 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_board. 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_board 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 →