刪除指定的 Azure DevOps Work Item 並將其移至回收站。
AI agents call delete_work_item to permanently remove resources in Azure Devops — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes work items from the system (even if moved to recycle bin, this is typically a destructive, non-easily-reversible operation in Azure DevOps). Deletion is irreversible by design and cannot be undone through normal tool operations. This is the most severe category applicable and represents significant blast radius if an AI agent mistakenly deletes critical work items.
From the tool's definition Tool name is 'delete_work_item' and description states it deletes a specified Azure DevOps Work Item and moves it to recycle bin ('刪除指定的 Azure DevOps Work Item 並將其移至回收站'). The word '刪除' (delete) indicates irreversible removal of data.
Attacks that exploit this kind of access
刪除指定的 Azure DevOps Work Item 並將其移至回收站。. It is categorised as a Destructive tool in the Azure Devops MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Azure Devops MCP server in PolicyLayer and add a rule for delete_work_item: 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. Nothing to install.
delete_work_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_work_item 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 delete_work_item. 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.
delete_work_item is provided by the Azure Devops MCP server (wuhuangjia/azure-devops-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 →