Get detailed information about a specific work item by ID
AI agents call get_work_item_details 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 data (work item details) without side effects. It follows the 'get' pattern characteristic of Read operations. Given the Azure DevOps context where work items are project metadata, exposure of this tool poses minimal risk—it surfaces information an authenticated user would typically access anyway in the normal course of work.
From the tool's definition Tool name 'get_work_item_details' and description 'Get detailed information about a specific work item by ID' indicate a retrieval operation. No modification, deletion, execution, or financial operation is described or implied.
Attacks that exploit this kind of access
Get detailed information about a specific work item by ID. 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_work_item_details: 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_work_item_details 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_work_item_details 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_work_item_details. 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_work_item_details 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 →