update_work_item · MCP Server for Azure DevOps MCP

WHAT IT DOES

What update_work_item does on MCP Server for Azure DevOps

AI agents use update_work_item to create or update resources in MCP Server for Azure DevOps — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server for Azure DevOps environment.

WHY IT NEEDS A POLICY

Why update_work_item needs a policy

This tool creates or modifies data reversibly by updating work item properties (status, assignment, description, etc.). Changes can be reverted through subsequent updates or undo operations. It does not execute code, delete data irreversibly, or move money. The medium severity reflects that misuse could disrupt team workflows or corrupt project tracking data, but changes remain reversible.

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 tracking system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_work_item Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_work_item": {
      "limits": [
        {
          "counter": "update_work_item_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Server for Azure DevOps, so you can run agents against it safely.

FAQ

Questions about update_work_item

What does the update_work_item tool do? +

Update an existing work item. It is categorised as a Write tool in the MCP Server for Azure DevOps MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_work_item? +

Register the MCP Server for Azure DevOps 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 MCP Server for Azure DevOps. Nothing to install.

What risk level is update_work_item? +

update_work_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_work_item? +

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.

How do I block update_work_item completely? +

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.

What MCP server provides update_work_item? +

update_work_item is provided by the MCP Server for Azure DevOps MCP server (sepal7/mcp-ado). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.