update_work_item_description · Azure DevOps MCP Server MCP

WHAT IT DOES

What update_work_item_description does on Azure DevOps MCP Server

AI agents use update_work_item_description 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.

WHY IT NEEDS A POLICY

Why update_work_item_description needs a policy

This tool creates or modifies data reversibly by updating a work item's description field. It does not delete data (which would be Destructive), does not execute arbitrary code (which would be Execute), and does not involve financial transactions.

From the tool's definition Tool name is 'update_work_item_description' and description states 'Update the description of a work item.' This modifies existing data (work item description) in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_work_item_description Rate-limited

update_work_item_description 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_description": {
      "limits": [
        {
          "counter": "update_work_item_description_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 Azure DevOps MCP Server, so you can run agents against it safely.

FAQ

Questions about update_work_item_description

What does the update_work_item_description tool do? +

Update the description of a 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.

How do I enforce a policy on update_work_item_description? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for update_work_item_description: 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.

What risk level is update_work_item_description? +

update_work_item_description 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_description? +

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

Set action: deny in the PolicyLayer policy for update_work_item_description. 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_description? +

update_work_item_description is provided by the Azure DevOps MCP Server MCP server (jhlia0/azure-devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.