Azure DevOps MCP Server for Cline

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

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

Last updated:

7 can modify or destroy data
8 read-only
15 tools total

Community server · catalogue entry verified 11/06/2026

How to control Azure DevOps MCP Server for Cline ↓

Read (8) Write / Execute (7) Destructive / Financial (0)
High Risk

7 of Azure DevOps MCP Server for Cline's 15 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 for Cline, 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_boards": {
    "limits": [
      {
        "counter": "get_boards_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 for Cline — 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.

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

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

The Azure DevOps MCP Server for Cline server has 6 write tools including create_pull_request, create_wiki, create_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 Azure DevOps MCP Server for Cline.

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

15 tools across 3 categories: Execute, Read, Write. 8 are read-only. 7 can modify, create, or delete data.

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

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

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

Free to start. No card required.

15 Azure DevOps MCP Server for Cline 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.