update_work_item_title · Azure DevOps MCP Server MCP

WHAT IT DOES

What update_work_item_title does on Azure DevOps MCP Server

AI agents use update_work_item_title 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_title needs a policy

This tool modifies work item metadata (title) reversibly within Azure DevOps. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), does not move money (not Financial), and does not irreversibly destroy information. The blast radius is moderate—a malicious agent could spam misleading titles across work items causing confusion and wasted effort, but changes are easily reverted.

From the tool's definition Tool name is 'update_work_item_title' and description states it 'Update[s] the title of a work item.' The verb 'update' indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_work_item_title Rate-limited

update_work_item_title 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_title": {
      "limits": [
        {
          "counter": "update_work_item_title_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_title

What does the update_work_item_title tool do? +

Update the title 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_title? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for update_work_item_title: 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_title? +

update_work_item_title 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_title? +

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

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

update_work_item_title 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.