Get all issues assigned to me in the current sprint
AI agents call get_my_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.
This tool retrieves and queries work item data (sprint issues assigned to the user) without creating, modifying, deleting, executing code, or moving money. It is a straightforward read operation that returns information from Azure DevOps.
From the tool's definition Tool name 'get_my_current_sprint_issues' and description 'Get all issues assigned to me in the current sprint' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get all issues assigned to me in the current sprint. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for get_my_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.
get_my_current_sprint_issues 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_my_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.
Set action: deny in the PolicyLayer policy for get_my_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.
get_my_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.
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 →