Azure DevOps MCP Server

42 tools. 11 can modify or destroy data without limits.

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

Last updated:

11 can modify or destroy data
31 read-only
42 tools total

Community server · catalogue entry verified 10/06/2026

How to control Azure DevOps MCP Server ↓

Read (31) Write / Execute (11) Destructive / Financial (0)
High Risk

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

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
{
  "pipeline_timeline": {
    "limits": [
      {
        "counter": "pipeline_timeline_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

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

Free to start. No card required.

READ 31 tools
Read pipeline_timeline Retrieve the timeline of stages and jobs for a pipeline run, to reduce the amount of data returned, you can fi Read download_pipeline_artifact Download a file from a pipeline run artifact and return its textual content Read get_all_repositories_tree Displays a hierarchical tree view of files and directories across multiple Azure DevOps repositories within a Read get_file_content Get content of a file or directory from a repository Read get_me Get details of the authenticated user (id, displayName, email) Read get_pipeline Get details of a specific pipeline Read get_pipeline_log Retrieve a specific pipeline log using the timeline log identifier Read get_pipeline_run Get details for a specific pipeline run Read get_project Get details of a specific project Read get_project_details Get comprehensive details of a project including process, work item types, and teams Read get_pull_request Get a pull request by ID (no repositoryId required; best for Azure DevOps Server where PR IDs are project-scop Read get_pull_request_changes Get the files changed in a pull request, their unified diffs, source/target branch names, and the status of po Read get_pull_request_comments Get comments from a specific pull request Read get_repository Get details of a specific repository Read get_repository_details Get detailed information about a repository including statistics and refs Read get_repository_tree Displays a hierarchical tree view of files and directories within a single repository starting from an optiona Read get_wiki_page Get the content of a wiki page Read get_wikis Get details of wikis in a project Read get_work_item Get details of a specific work item Read list_commits List recent commits on a branch including file-level diff content for each commit Read list_organizations List all Azure DevOps organizations accessible to the current authentication Read list_pipeline_runs List recent runs for a pipeline Read list_pipelines List pipelines in a project Read list_projects List all projects in an organization Read list_pull_requests List pull requests in a repository Read list_repositories List repositories in a project Read list_wiki_pages List pages within an Azure DevOps wiki Read list_work_items List work items in a project Read search_code Search for code across repositories in a project Read search_wiki Search for content across wiki pages in a project Read search_work_items Search for work items across projects in Azure DevOps

Other MCP servers with similar tools — same risk classification, starter policies for each.

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

The Azure DevOps MCP Server server has 10 write tools including add_pull_request_comment, create_branch, create_pull_request. 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? +

42 tools across 3 categories: Execute, Read, Write. 31 are read-only. 11 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 42 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.