AI agents use update_work_item to create or update resources in Azure DevOps MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps MCP Server environment.
The tool creates or modifies data reversibly rather than deleting it irreversibly or executing arbitrary code. Updates to work items (status, assignee, description, etc.) are typical Write operations. Severity is medium because misuse could affect project tracking and team coordination, but the impact is contained to metadata/state changes rather than critical infrastructure or financial transactions.
From the tool's definition Tool name 'update_work_item' and description 'Update an existing work item' indicate modification of existing data in Azure DevOps work items. This is a reversible write operation—changes can be undone through subsequent updates or version history recovery.
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, 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. It is categorised as a Write tool in the Azure DevOps MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure DevOps MCP Server 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. 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 MCP server (tiberriver256/mcp-server-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Azure DevOps MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.