Azure Devops

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

2 destructive tools with no built-in limits. Policy required.

Last updated:

7 can modify or destroy data
6 read-only
13 tools total

Community server · catalogue entry verified 03/07/2026

How to control Azure Devops ↓

What Azure Devops exposes to your agents

Read (6) Write / Execute (5) Destructive / Financial (2)
Critical Risk

The most dangerous Azure Devops tools

7 of Azure Devops's 13 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Azure Devops

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

Deny destructive operations
{
  "batch_update_work_items": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add_issue_comment": {
    "limits": [
      {
        "counter": "add_issue_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_project_details": {
    "limits": [
      {
        "counter": "get_project_details_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 — 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 →

Instant setup, no code required.

All 13 Azure Devops tools

Related servers

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

Questions about Azure Devops

Can an AI agent delete data through the Azure Devops MCP server? +

Yes. The Azure Devops server exposes 2 destructive tools including batch_update_work_items, delete_work_item. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Azure Devops? +

The Azure Devops server has 5 write tools including add_issue_comment, create_work_item, link_commit_to_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.

How many tools does the Azure Devops MCP server expose? +

13 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Azure Devops? +

Register the 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 Azure Devops tool call.

Deterministic rules across all 13 Azure Devops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

13 Azure Devops tools catalogued and risk-classified — across an index of 43,000+ 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.