批次更新多個 Azure DevOps Work Items。可在單一請求中執行多個建立、更新或刪除操作。
AI agents call batch_update_work_items 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.
The tool explicitly supports delete operations in batch, which is irreversible. Since it can perform destructive deletions across multiple work items in a single request, the most severe applicable category is Destructive. The blast radius is high because a single misuse could irrecoverably delete many work items at once.
From the tool's definition 批次更新多個 Azure DevOps Work Items。可在單一請求中執行多個建立、更新或刪除操作 (can execute multiple create, update, or DELETE operations in a single request)
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
批次更新多個 Azure DevOps Work Items。可在單一請求中執行多個建立、更新或刪除操作。. 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 batch_update_work_items: 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.
batch_update_work_items 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 batch_update_work_items 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 batch_update_work_items. 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.
batch_update_work_items 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 →