// SCAN REPORT

Azure DevOps MCP Server

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

1 write tool that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 04/07/2026

How to control Azure DevOps MCP Server ↓

TOOL MAP

What Azure DevOps MCP Server exposes to your agents

Read (2) Write / Execute (1) 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

Execute · Medium query_work_items The tool executes arbitrary WIQL queries, which is an Execute-category action.

1 of Azure DevOps MCP Server's 3 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:

Cap read operations

{
  "get_projects": {
    "limits": [
      {
        "counter": "get_projects_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 3 Azure DevOps MCP Server tools

EXECUTE 1 tools

Execute query_work_items Execute a WIQL query against Azure DevOps work items

READ 2 tools

Read get_projects Fetch all Azure DevOps projects in the organization Read get_ticket_count Counts Azure DevOps tickets by state (New, Active, Resolved, Closed)

FAQ

Questions about Azure DevOps MCP Server

Is the Azure DevOps MCP Server MCP server safe to use without restrictions? +

The Azure DevOps MCP Server server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

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

3 tools across 1 categories: Read. 2 are read-only. 1 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 3 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.

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