create_work_item · MCP Server for Azure DevOps MCP

WHAT IT DOES

What create_work_item does on MCP Server for Azure DevOps

AI agents use create_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 create_work_item needs a policy

This tool creates new work items (tasks, bugs, features, etc.) in Azure DevOps, which modifies the project state reversibly—work items can be edited or deleted later. It does not execute code, trigger pipelines, delete data irreversibly, or move money.

From the tool's definition Tool name 'create_work_item' and description 'Create a new work item' indicate creation of data in Azure DevOps work tracking system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_work_item Rate-limited

create_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": {
    "create_work_item": {
      "limits": [
        {
          "counter": "create_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 create_work_item

What does the create_work_item tool do? +

Create a new 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 create_work_item? +

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

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

Can I rate-limit create_work_item? +

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

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

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

// THE FULL RECORD

create_work_item is one line of MCP Server for Azure DevOps's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →