Get project work item metadata context: types, labels, members, and optional field/workflow configuration for one type. Use this before creating or updating work items to discover valid IDs for status, priority, labels, and members.
AI agents call get_project_workitem_context 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 labels. Defaults to 1. |
perPage | number | — | Page size for labels. Defaults to 20. |
category | string | Yes | Work item category, such as Req, Task, Bug, or Risk. |
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
includeFields | boolean | — | Whether to include field configuration when workItemTypeId is set. Defaults to true. |
includeLabels | boolean | — | Whether to include project labels. Defaults to true. |
includeMembers | boolean | — | Whether to include project members. Defaults to true. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
workItemTypeId | string | — | Optional work item type ID (numeric string) for field and workflow metadata. Use list_work_item_types to find available types. |
includeWorkflow | boolean | — | Whether to include workflow metadata when workItemTypeId is set. Defaults to true. |
Parameters from the server's own tool schema.
This tool retrieves metadata (types, labels, members, field/workflow configuration) from the Yunxiao DevOps platform without creating, modifying, or deleting any data. It serves as an informational lookup to understand valid values for subsequent operations. No side effects occur from calling this tool.
From the tool's definition Tool description states it 'Get[s] project work item metadata context' and is used 'before creating or updating work items to discover valid IDs'.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Get project work item metadata context: types, labels, members, and optional field/workflow configuration for one type. Use this before creating or updating work items to discover valid IDs for status, priority, labels, and members. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_project_workitem_context accepts 10 parameters: page, perPage, category, projectId, includeFields, includeLabels, includeMembers, organizationId, workItemTypeId, includeWorkflow. 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_context: 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_context 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_context 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_context. 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_context 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 →