link_commit_to_work_item · Azure Devops MCP: Risk & Policy

WHAT IT DOES

What link_commit_to_work_item does on Azure Devops

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

WHY IT NEEDS A POLICY

Why link_commit_to_work_item needs a policy

Linking a commit to a work item creates a new relationship/reference that did not exist before. This is a reversible write operation—the link can be removed later. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool name 'link_commit_to_work_item' and description indicating it links Git commits to Azure DevOps work items. This creates/establishes a relationship between two entities (a commit and a work item), which is a modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

link_commit_to_work_item Rate-limited

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

FAQ

Questions about link_commit_to_work_item

What does the link_commit_to_work_item tool do? +

將 Git Commit 連結到 Azure DevOps Work Item。. It is categorised as a Write tool in the 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 link_commit_to_work_item? +

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

What risk level is link_commit_to_work_item? +

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

Can I rate-limit link_commit_to_work_item? +

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

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

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