add_work_item_relation · Azure DevOps MCP Server MCP

WHAT IT DOES

What add_work_item_relation does on Azure DevOps MCP Server

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

This tool creates or establishes new relationships/links between work items, which is a reversible modification operation. It does not execute arbitrary code, delete data, move money, or retrieve data. The blast radius is medium because incorrect relationships could confuse project tracking, but the operation is reversible (relationships can be removed).

From the tool's definition Tool name 'add_work_item_relation' and description 'Add a relationship between work items' indicate creation of a new relational connection between existing work items. This is a write operation that modifies work item metadata reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_work_item_relation Rate-limited

add_work_item_relation 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": {
    "add_work_item_relation": {
      "limits": [
        {
          "counter": "add_work_item_relation_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 add_work_item_relation

What does the add_work_item_relation tool do? +

Add a relationship between work items. 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 add_work_item_relation? +

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

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

Can I rate-limit add_work_item_relation? +

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

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

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