list_all_current_sprint_issues

List all issues 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_issues does on Azure DevOps MCP Server

AI agents call list_all_current_sprint_issues 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_issues needs a policy

This tool purely reads and retrieves sprint issue data from Azure DevOps. It has no side effects, does not modify any state, does not execute code or commands, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could only retrieve existing sprint information that would typically be accessible to the user anyway. This clearly falls under the Read category.

From the tool's definition Tool name contains 'list' and description states 'List all issues in the current sprint with summary information'. This retrieves and displays data without modification, deletion, or execution of external operations.

Questions about list_all_current_sprint_issues

What does the list_all_current_sprint_issues tool do? +

List all issues 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_issues? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for list_all_current_sprint_issues: 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_issues? +

list_all_current_sprint_issues 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_issues? +

Yes. Add a rate_limit block to the list_all_current_sprint_issues 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_issues completely? +

Set action: deny in the PolicyLayer policy for list_all_current_sprint_issues. 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_issues? +

list_all_current_sprint_issues 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.

// THE FULL RECORD

list_all_current_sprint_issues is one line of Azure DevOps MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.