Search work items in a single Projex project with flexible filtering and pagination. This is the primary tool for finding work items when you know the project. For a high-level summary across categories without detailed filtering, use get_project_workitem_summary. For a Kanban board view grouped ...
AI agents call search_workitems 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. Use get_project_workitem_context to discover available tags. |
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction: asc (ascending) or desc (descending). |
sprint | string | — | Comma-separated sprint IDs. Use list_sprints to discover sprint IDs in the project. |
status | string | — | Comma-separated status IDs. Use get_project_workitem_context to discover valid status IDs for the target category. |
creator | string | — | Comma-separated creator user IDs. Use list_project_members to find user IDs in the project. |
orderBy | string | — | Sort field. Defaults are controlled by Yunxiao. Common values: gmtCreate, gmtModified, priority, serialNumber. |
perPage | number | — | Page size for pagination. Most endpoints default to 20. |
subject | string | — | Filter by work item subject/title (contains match). |
category | string | Yes | Work item category. Common values: Req (需求/Requirement), Task (任务), Bug (缺陷), Risk (风险). Use list_work_item_types to discover available categories for a project |
priority | string | — | Comma-separated priority IDs. Use get_project_workitem_context to discover available priorities. |
projectId | string | Yes | Project ID (string). This API searches one project at a time. Use search_projects to find the project ID. |
Parameters from the server's own tool schema.
This tool retrieves and queries work item data from a Projex project. The core function is to search and filter existing work items, which is a read-only operation with no side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal — an agent could potentially retrieve sensitive work item data if it exists in the project, but cannot modify or destroy anything.
From the tool's definition Tool name 'search_workitems' and description explicitly states it 'Search work items' with 'flexible filtering and pagination'.
Risk signalsHigh parameter count (26 properties)
Attacks that exploit this kind of access
Search work items in a single Projex project with flexible filtering and pagination. This is the primary tool for finding work items when you know the project. For a high-level summary across categories without detailed filtering, use get_project_workitem_summary. For a Kanban board view grouped by status, use get_project_workitem_board. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
search_workitems accepts 12 parameters: tag, page, sort, sprint, status, creator, orderBy, perPage, subject, category, priority, projectId. 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 search_workitems: 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.
search_workitems 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 search_workitems 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 search_workitems. 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.
search_workitems 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 →