Get aggregated dependency blocker analysis for a project including work items that are blocked by unresolved dependencies and work items that are blocking others. Useful for identifying critical path risks and unblocking the team.
AI agents call get_blocker_analysis 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 to analyze. Defaults to Task,Bug. |
sampleLimit | number | — | Max work items to analyze per category. Defaults to 20, 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.
The tool retrieves and analyzes existing blocker and dependency data from the DevOps platform to provide insights. It produces no side effects, creates no new data, executes no external operations, and does not delete or modify anything. This is a pure data retrieval and aggregation operation, fitting the Read category with low risk.
From the tool's definition Tool description explicitly states 'Get aggregated dependency blocker analysis' and 'identifying critical path risks' — these are read operations that retrieve and analyze existing project data about blocked/blocking work items and dependencies.
Attacks that exploit this kind of access
Get aggregated dependency blocker analysis for a project including work items that are blocked by unresolved dependencies and work items that are blocking others. Useful for identifying critical path risks and unblocking the team. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_blocker_analysis accepts 4 parameters: projectId, categories, sampleLimit, 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_blocker_analysis: 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_blocker_analysis 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_blocker_analysis 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_blocker_analysis. 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_blocker_analysis 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 →