// SCAN REPORT

MCP Server for Azure DevOps

25 tools. 3 can modify or destroy data without limits.

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

Last updated: 4 Jul 2026

3 can modify or destroy data

22 read-only

25 tools total

Community server · catalogue entry verified 04/07/2026

How to control MCP Server for Azure DevOps ↓

TOOL MAP

What MCP Server for Azure DevOps exposes to your agents

Read (22) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Server for Azure DevOps tools

Execute · Critical ado_api_call A generic API call tool can invoke any Azure DevOps REST endpoint with any HTTP method (GET, POST, PUT, PATCH, DELETE), enabling arbitrary reads, writes, deletions, pipeline triggers, and more. Write · Medium create_work_item 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. Write · Medium update_work_item This tool creates or modifies data reversibly by updating work item properties (status, assignment, description, etc.).

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

POLICY

How to control MCP Server for Azure DevOps

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

Rate limit write operations

{
  "create_work_item": {
    "limits": [
      {
        "counter": "create_work_item_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_build": {
    "limits": [
      {
        "counter": "get_build_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 MCP Server for Azure DevOps — 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 MCP SERVER FOR AZURE DEVOPS →

Instant setup, no code required.

FULL CATALOGUE

All 25 MCP Server for Azure DevOps tools

EXECUTE 1 tools

Execute ado_api_call Make a generic Azure DevOps REST API call

WRITE 2 tools

Write create_work_item Create a new work item Write update_work_item Update an existing work item

READ 22 tools

Read get_build Get build details by ID Read get_pipeline_run Get pipeline run details Read get_pr_comments Get pull request review comments Read get_pull_request Get pull request details Read get_release Get release details Read get_repo Get repository details by name Read get_repo_file Get file content from a repository Read get_test_plan Get test plan details Read get_wiki_page Retrieve a specific Azure DevOps wiki page by ID or path Read get_work_item Get work item details by ID Read get_work_items Get multiple work items by IDs Read list_builds List recent builds Read list_pipelines List pipelines in the project Read list_pull_requests List pull requests in a repository Read list_releases List releases Read list_repo_branches List branches in a repository Read list_repos List all repositories in the project Read list_test_plans List test plans Read list_wiki_pages List all pages in a wiki Read query_work_items Query work items using WIQL (Work Item Query Language) Read search_code Search code across repositories Read search_wiki_pages Search wiki pages by content or title

FAQ

Questions about MCP Server for Azure DevOps

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

The MCP Server for Azure DevOps server has 2 write tools including create_work_item, update_work_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 MCP Server for Azure DevOps.

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

25 tools across 2 categories: Read, Write. 22 are read-only. 3 can modify, create, or delete data.

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

Register the MCP Server for Azure DevOps 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 MCP Server for Azure DevOps tool call.

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

ENFORCE POLICY ON MCP SERVER FOR AZURE DEVOPS →

Instant setup, no code required.

25 MCP Server for Azure DevOps tools catalogued and risk-classified — across an index of 43,000+ MCP servers.