List sprints (iterations) in a Projex project. Sprints are time-boxed development cycles. Use this when you need iteration-level planning data. For a broader view that also includes milestones and versions, use get_project_overview instead.
AI agents call list_sprints 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 |
|---|---|---|---|
name | string | — | Filter by sprint name (contains match). |
page | number | — | Page number for pagination. Starts at 1. |
status | string | — | Comma-separated sprint statuses. Common values: TODO (not started), DOING (active), ARCHIVED (closed). |
perPage | number | — | Page size for pagination. Most endpoints default to 20. |
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 retrieves and queries sprint information from a DevOps project management platform. It performs a read-only operation that retrieves existing data structures without creating, modifying, or deleting anything. The suggestion to use 'get_project_overview' for a broader view further confirms this is a data retrieval tool. No side effects or irreversible actions are possible with this tool.
From the tool's definition Tool name 'list_sprints' and description 'List sprints' indicates retrieval of sprint/iteration data. Description explicitly states this is for querying 'iteration-level planning data' with no mention of modifications, deletions, or side effects.
Attacks that exploit this kind of access
List sprints (iterations) in a Projex project. Sprints are time-boxed development cycles. Use this when you need iteration-level planning data. For a broader view that also includes milestones and versions, use get_project_overview instead. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_sprints accepts 6 parameters: name, page, status, perPage, projectId, organizationId. Required: 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_sprints: 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_sprints 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_sprints 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_sprints. 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_sprints 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 →