list_all_current_sprint_tickets

List all work items in the current sprint with summary information

Server Azure DevOps MCP Server linhdangopti/mcpserver
Category Read
Risk class Low
Parameters 00 required

What list_all_current_sprint_tickets does on Azure DevOps MCP Server

AI agents call list_all_current_sprint_tickets to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_all_current_sprint_tickets needs a policy

This tool retrieves sprint work item data for display purposes only. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. The blast radius of misuse is minimal—an attacker could only view sprint information already accessible to authenticated Azure DevOps users. This is a straightforward Read operation.

From the tool's definition Tool name and description indicate it 'List[s] all work items in the current sprint with summary information' - a read-only query operation that retrieves and displays existing sprint data without modification, deletion, or execution of external operations.

Questions about list_all_current_sprint_tickets

What does the list_all_current_sprint_tickets tool do? +

List all work items in the current sprint with summary information. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_all_current_sprint_tickets? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for list_all_current_sprint_tickets: 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 Azure DevOps MCP Server. Nothing to install.

What risk level is list_all_current_sprint_tickets? +

list_all_current_sprint_tickets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_all_current_sprint_tickets? +

Yes. Add a rate_limit block to the list_all_current_sprint_tickets 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.

How do I block list_all_current_sprint_tickets completely? +

Set action: deny in the PolicyLayer policy for list_all_current_sprint_tickets. 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.

What MCP server provides list_all_current_sprint_tickets? +

list_all_current_sprint_tickets is provided by the Azure DevOps MCP Server MCP server (linhdangopti/mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.