Update an existing work item using JSON patch operations
AI agents use update_work_item to create or update resources in Azure DevOps MCP Server for Cline — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps MCP Server for Cline environment.
This tool creates or modifies data in a reversible manner (work items can be updated again or reverted). It is not destructive (no deletion), not financial, and not execute-class (no arbitrary code/command execution).
From the tool's definition Tool name includes 'update' and description states 'Update an existing work item using JSON patch operations', which modifies data reversibly without deletion.
Documented attack patterns abuse exactly the kind of access update_work_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server for Cline, and nothing reaches the server without passing your rules. This is the rule we recommend for update_work_item:
{
"version": "1",
"default": "deny",
"tools": {
"update_work_item": {
"limits": [
{
"counter": "update_work_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_work_item stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing work item using JSON patch operations. It is categorised as a Write tool in the Azure DevOps MCP Server for Cline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure DevOps MCP Server for Cline MCP server in PolicyLayer and add a rule for update_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 MCP Server for Cline. Nothing to install.
update_work_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_work_item is provided by the Azure DevOps MCP Server for Cline MCP server (stefanskiasan/azure-devops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Azure DevOps MCP Server for Cline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Azure DevOps MCP Server for Cline tools catalogued and risk-classified — across an index of 42,500+ MCP servers.