// SCAN REPORT

Az Devops Cli

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

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

Last updated: 3 Jul 2026

7 can modify or destroy data

6 read-only

13 tools total

Community server · catalogue entry verified 03/07/2026

How to control Az Devops Cli ↓

TOOL MAP

What Az Devops Cli exposes to your agents

Read (6) Write / Execute (7) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Az Devops Cli tools

Write · Medium add_comment Adding a comment creates new data and modifies the work item record, but the operation is fully reversible (comments can be deleted or edited). Write · High create_pr The tool creates a new pull request, which is a reversible write operation (PRs can be closed or abandoned). Write · Medium create_work_item This tool creates new data structures (work items) in Azure DevOps but does not delete, execute arbitrary code, or move money. Write · Medium link_pr_to_work_item This tool creates a linkage between a pull request and a work item, which is a reversible write operation (the link can be removed).

7 of Az Devops Cli'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 Az Devops Cli

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

Rate limit write operations

{
  "add_comment": {
    "limits": [
      {
        "counter": "add_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_pr": {
    "limits": [
      {
        "counter": "get_pr_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 Az Devops Cli — 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 AZ DEVOPS CLI →

Instant setup, no code required.

FULL CATALOGUE

All 13 Az Devops Cli tools

WRITE 7 tools

Write add_comment Add a discussion comment to a work item. Use to log agent reasoning or decisions. Write create_pr Create a pull request. Write create_work_item Create a work item on the board. type options: Task, Bug, User Story, Epic, Feature. Write link_pr_to_work_item Link a PR to a work item for full board-to-code traceability. Call every time a PR is raised. Write link_work_items Link two work items. link_type options: Related, Parent, Child, Duplicate, Successor, Predecessor. Write set_iteration Assign a work item to a sprint iteration. Write update_work_item Update state, assignment, or title of a work item.

READ 6 tools

Read get_pr Get full details of a specific PR. Read get_work_item Get a work item by ID. Read get_work_item_relations Get all linked work items. Use after bulk linking to verify hierarchy. Read list_branches List all branches in a repository. Read list_prs List pull requests in a project. status options: active, completed, abandoned, all. Read query_work_items Run a WIQL query to find work items. Use for any bulk lookups.

FAQ

Questions about Az Devops Cli

How do I prevent bulk modifications through Az Devops Cli? +

The Az Devops Cli server has 7 write tools including add_comment, create_pr, 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 Az Devops Cli.

How many tools does the Az Devops Cli MCP server expose? +

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

How do I enforce a policy on Az Devops Cli? +

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

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

ENFORCE POLICY ON AZ DEVOPS CLI →

Instant setup, no code required.

13 Az Devops Cli tools catalogued and risk-classified — across an index of 43,000+ MCP servers.