AI agents call list_work_item_types 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 |
|---|---|---|---|
category | string | Yes | Work item category to filter by. Common values: Req, Bug, Task, Risk. Use list_all_work_item_types to see available categories. |
projectId | string | Yes | Project ID (string). Use search_projects if you do not know the project ID. |
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 metadata about available work item types in a Projex project. It performs no modifications, deletions, or external operations. It is purely informational, supporting discovery before other operations. This is a straightforward Read category tool with low blast radius.
From the tool's definition Tool name 'list_work_item_types' and description states it 'List work item types available' and is used to 'discover valid workitemTypeId values' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List work item types available in a specific Projex project. Use this before creating a work item to discover valid workitemTypeId values and categories for the target project. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_work_item_types accepts 3 parameters: category, projectId, 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 list_work_item_types: 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.
list_work_item_types 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 list_work_item_types 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 list_work_item_types. 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.
list_work_item_types 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 →