ado_update_work_item · Mcp Azure MCP: Risk & Policy

WHAT IT DOES

What ado_update_work_item does on Mcp Azure

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

WHY IT NEEDS A POLICY

Why ado_update_work_item needs a policy

This tool creates or modifies data reversibly within Azure DevOps. Updating work items (changing status, fields, assignments, etc.) is a standard Write operation. It's reversible—changes can be undone or corrected. The severity is medium because misuse could cause workflow disruption or incorrect project state, but no data is permanently deleted and financial impact is unlikely without chaining to other tools.

From the tool's definition Tool name 'ado_update_work_item' and description 'Actualiza un Work Item existente en Azure DevOps' (Updates an existing Work Item in Azure DevOps) indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ado_update_work_item Rate-limited

ado_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": {
    "ado_update_work_item": {
      "limits": [
        {
          "counter": "ado_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 Azure, so you can run agents against it safely.

FAQ

Questions about ado_update_work_item

What does the ado_update_work_item tool do? +

Actualiza un Work Item existente en Azure DevOps. It is categorised as a Write tool in the Mcp Azure MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ado_update_work_item? +

Register the Mcp Azure MCP server in PolicyLayer and add a rule for ado_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 Azure. Nothing to install.

What risk level is ado_update_work_item? +

ado_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 ado_update_work_item? +

Yes. Add a rate_limit block to the ado_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 ado_update_work_item completely? +

Set action: deny in the PolicyLayer policy for ado_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 ado_update_work_item? +

ado_update_work_item is provided by the Mcp Azure MCP server (soulberto/mcp-azure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.