Update an existing work item in Azure DevOps
AI agents use update-work-item to create or update resources in DevOps Enhanced MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DevOps Enhanced MCP environment.
The tool modifies existing Azure DevOps work items (tickets, tasks, etc.), which is a Write operation—data is changed but the modification is reversible (can be updated again or rolled back). Severity is medium because misuse could alter project tracking data, affect team visibility, or cause workflow disruption, but the scope is limited to individual work items rather than system-wide or financial impact.
From the tool's definition Tool name 'update-work-item' and description 'Update an existing work item in Azure DevOps' indicate modification of existing data in a reversible manner. The action creates or modifies work item metadata, status, or content 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 DevOps Enhanced MCP, 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 in Azure DevOps. It is categorised as a Write tool in the DevOps Enhanced MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DevOps Enhanced 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 DevOps Enhanced MCP. 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 DevOps Enhanced MCP server (wangkanai/devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DevOps Enhanced MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 DevOps Enhanced MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.