Get historical sprint velocity metrics including completion rates, work item counts, and trend analysis per sprint. Combines sprint metadata with categorized work item completion statistics. Useful for sprint planning and delivery forecasting.
AI agents call get_sprint_velocity 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 |
|---|---|---|---|
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
categories | string | — | Comma-separated work item categories for velocity calculation. Defaults to Task,Bug. |
sprintCount | number | — | Number of recent sprints to analyze. Defaults to 5, max 20. |
sprintStatus | string | — | Comma-separated sprint statuses to include. Defaults to ARCHIVED,DONE. |
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 purely queries and retrieves existing sprint metrics and analytics data. It performs read-only operations on historical project management data. There are no side effects, data modifications, code execution, deletions, or financial implications. The use case (sprint planning and delivery forecasting) confirms it is a passive analytics tool.
From the tool's definition Tool retrieves historical sprint velocity metrics including completion rates, work item counts, and trend analysis per sprint.
Attacks that exploit this kind of access
Get historical sprint velocity metrics including completion rates, work item counts, and trend analysis per sprint. Combines sprint metadata with categorized work item completion statistics. Useful for sprint planning and delivery forecasting. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_sprint_velocity accepts 5 parameters: projectId, categories, sprintCount, sprintStatus, 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 get_sprint_velocity: 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_sprint_velocity 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_sprint_velocity 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_sprint_velocity. 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_sprint_velocity 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 →