// SCAN REPORT

Azure DevOps MCP Server

16 tools. 7 can modify or destroy data without limits.

7 write tools that can modify data. Rate limits recommended.

Last updated: 15 Aug 2026

7 can modify or destroy data

9 read-only

16 tools total

Community server · catalogue entry checked 15/08/2026

How to control Azure DevOps MCP Server ↓

TOOL MAP

What Azure DevOps MCP Server exposes to your agents

Read (9) Write / Execute (7) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Azure DevOps MCP Server tools

Write · Medium add_pull_request_comment Adding comments to pull requests is a reversible write operation that modifies PR metadata/discussions but does not alter code, delete data, or execute arbitrary logic. Write · Medium create_bug Creating a bug work item in Azure DevOps is a write operation—it creates new data (a bug record) reversibly, as bugs can be deleted or modified later. Write · Medium create_product_backlog_item This tool creates a new product backlog item in Azure DevOps, which is a reversible write operation. Write · High create_pull_request Creating a pull request is a reversible write operation—it commits code for review and can be closed, abandoned, or modified afterward, but does not permanently delete data or execute arbitrary code.

7 of Azure DevOps MCP Server's 16 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Azure DevOps MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "add_pull_request_comment": {
    "limits": [
      {
        "counter": "add_pull_request_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_pull_request": {
    "limits": [
      {
        "counter": "get_pull_request_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Azure DevOps MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON AZURE DEVOPS →

Instant setup, no code required.

FULL CATALOGUE

All 16 Azure DevOps MCP Server tools

WRITE 7 tools

Write add_pull_request_comment add_pull_request_comment Write create_bug create_bug Write create_product_backlog_item create_product_backlog_item Write create_pull_request create_pull_request Write create_work_item create_work_item Write link_pr_to_work_item link_pr_to_work_item Write set_pr_description set_pr_description

READ 9 tools

Read get_pull_request get_pull_request Read get_pull_request_full_diff get_pull_request_full_diff Read list_area_paths list_area_paths Read list_branches list_branches Read list_iteration_paths list_iteration_paths Read list_projects list_projects Read list_pull_requests list_pull_requests Read list_work_item_types list_work_item_types Read resolve_repo_id resolve_repo_id

FAQ

Questions about Azure DevOps MCP Server

How do I prevent bulk modifications through Azure DevOps MCP Server? +

The Azure DevOps MCP Server server has 7 write tools including add_pull_request_comment, create_bug, create_product_backlog_item. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Azure DevOps MCP Server.

How many tools does the Azure DevOps MCP Server MCP server expose? +

16 tools across 2 categories: Read, Write. 9 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Azure DevOps MCP Server? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Azure DevOps MCP Server tool call.

Deterministic rules across all 16 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON AZURE DEVOPS →

Instant setup, no code required.

16 Azure DevOps MCP Server tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Azure DevOps MCP Server's registry record.

The record behind this page: 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 →