AI agents call get_sprint_overview 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 |
|---|---|---|---|
status | string | — | Comma-separated status IDs applied to every category. |
creator | string | — | Comma-separated creator user IDs applied to every category. |
subject | string | — | Subject contains filter applied to every category. |
sprintId | string | Yes | Sprint ID (string). Use list_sprints to discover sprint IDs in the project. |
projectId | string | Yes | Project ID. Use search_projects to discover valid IDs. |
assignedTo | string | — | Comma-separated assignee user IDs applied to every category. |
categories | string | — | Comma-separated work item categories. Defaults to Task,Bug. |
sampleLimit | number | — | Samples returned per category. Defaults to 5, clamped to 0-200. |
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 aggregates sprint planning data (metadata, work items, summaries) from the Yunxiao DevOps platform. It performs no mutations, deletions, or command execution. The verb 'Get' and the read-only nature of aggregating summaries classify this as a Read operation with low severity—misuse would only expose planning information without operational impact.
From the tool's definition Tool description states 'Get a sprint overview' and 'Combines sprint metadata with categorized work item summaries' — purely retrieval operations with no modification, deletion, or execution of external processes.
Attacks that exploit this kind of access
Get a sprint overview with work item samples and totals by category for one project sprint. Combines sprint metadata with categorized work item summaries in a single call. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_sprint_overview accepts 9 parameters: status, creator, subject, sprintId, projectId, assignedTo, categories, sampleLimit, organizationId. Required: sprintId, 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_overview: 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_overview 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_overview 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_overview. 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_overview 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 →