// SCAN REPORT

azure-devops MCP Server

13 tools. 6 can modify or destroy data without limits.

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

Last updated: 29 Jun 2026

6 can modify or destroy data

7 read-only

13 tools total

Community server · catalogue entry verified 29/06/2026

How to control azure-devops MCP Server ↓

TOOL MAP

What azure-devops MCP Server exposes to your agents

Read (7) Write / Execute (6) 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 · High create_pull_request This tool creates new pull requests in Azure DevOps, which is a reversible modification of project state. Write · Medium create_pull_request_comment This tool creates new data (a comment) in a reversible manner. Write · Medium create_wiki_page This tool creates new wiki pages, which is a reversible write operation. Write · Medium create_work_item This tool creates new data (a work item) in Azure DevOps, which is a reversible operation.

6 of azure-devops MCP Server's 13 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

{
  "create_pull_request": {
    "limits": [
      {
        "counter": "create_pull_request_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_project": {
    "limits": [
      {
        "counter": "get_project_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 13 azure-devops MCP Server tools

WRITE 6 tools

Write create_pull_request Create a new pull request Write create_pull_request_comment Add a comment to a pull request Write create_wiki_page Create a new wiki page Write create_work_item Create a new work item Write edit_wiki_page Edit an existing wiki page Write update_pull_request Update an existing pull request

READ 7 tools

Read get_project Get details of a specific Azure DevOps project Read get_pull_request Get details of a specific pull request Read get_pull_request_diff Get the diff for a pull request Read get_work_item Get details of a specific work item Read list_projects List all accessible projects in the Azure DevOps organization Read list_pull_requests List pull requests in a repository Read list_work_items List work items in a project

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 6 write tools including create_pull_request, create_pull_request_comment, create_wiki_page. 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? +

13 tools across 2 categories: Read, Write. 7 are read-only. 6 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 13 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.

13 azure-devops MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.