// MCP TOOL REFERENCE

AZURE DEVOPS TOOLS

97 tools from the Azure Devops MCP Server, categorised by risk level.

// ALL 97 AZURE DEVOPS TOOLS

READ 57 tools

Read predictBuildFailures Predict potential build failures before they occur Read auditSecretUsage Audit usage of secrets across services Read browseRepository Browse the contents of a repository Read checkPackageDependencies Check package dependencies and vulnerabilities Read getAICodeReview Get AI-based code review suggestions Read getAreas Get areas for a project Read getBoardColumns Get columns for a specific board Read getBoardItems Get items on a specific board Read getBoards Get all boards for a team Read getCodeQualityTrends Track code quality trends over time Read getCommitHistory Get commit history for a repository Read getComplianceStatus Get current compliance status Read getContainerImageTags Get tags for a container image Read getCurrentSprint Get the current sprint Read getDeveloperProductivity Measure developer productivity metrics Read getExploratoryTestStatistics Get statistics on exploratory testing activities Read getFileContent Get the content of a file Read getIterations Get iterations for a project Read getMyWorkItems Get work items assigned to you Read getPackageVersions Get versions of a package in a feed Read getPredictiveBugAnalysis Predict potential bugs in code changes Read getPredictiveEffortEstimation AI-based effort estimation for work items Read getProcesses Get all processes Read getProjectDetails Get details of a specific project Read getPullRequest Get details of a specific pull request Read getPullRequestChangedFiles Get changed files in a pull request Read getPullRequestComments Get comments on a pull request Read getRecentlyUpdatedWorkItems Get recently updated work items Read getRepository Get details of a specific repository Read getSecurityScanResults Get results from security scans Read getSprintCapacity Get capacity for a specific sprint Read getSprints Get all sprints for a team Read getSprintWorkItems Get work items in a specific sprint Read getTeamMembers Get members of a team Read getTestAutomationStatus Check status of automated test execution Read getTestFlakiness Analyze and report on test flakiness Read getTestGapAnalysis Identify gaps in test coverage Read getTestHealthDashboard View overall test health metrics Read getWorkItemById Get a specific work item by ID Read getWorkItemTypeFields Get fields for a work item type Read getWorkItemTypes Get work item types for a process Read identifyCodeSmells Identify potential code smells and anti-patterns Read listArtifactFeeds List artifact feeds in the organization Read listBranches List branches in a repository Read listContainerImages List container images in a repository Read listProjects List all projects Read listPullRequests List pull requests Read listRepositories List all repositories Read listWorkItems List work items based on a WIQL query Read scanContainerImage Scan a container image for vulnerabilities and compliance issues Read searchCode Search for code in repositories Read searchWorkItems Search for work items by text Read suggestAutomationOpportunities Identify opportunities for automation Read suggestCodeOptimization Suggest code optimizations using AI Read suggestWorkItemRefinements Get AI suggestions for work item refinements Read trackSecurityAwareness Track security awareness and training Read generateSecurityCompliance Generate security compliance reports

WRITE 30 tools

Write integrateSarifResults Import and process SARIF format security results Write recordExploratoryTestResults Record findings during exploratory testing Write addWorkItemComment Add a comment to a work item Write approvePullRequest Approve a pull request Write assignWorkItem Assign a work item to a user Write bulkCreateWorkItems Create or update multiple work items in a single operation Write configureTestAgents Configure and manage test agents Write convertFindingsToWorkItems Convert exploratory test findings to work items Write createArea Create a new area in a project Write createComplianceReport Create compliance reports for auditing Write createExploratorySessions Create new exploratory testing sessions Write createIntelligentAlerts Set up intelligent alerts based on patterns Write createIteration Create a new iteration in a project Write createLink Create a link between work items Write createPackageDownloadReport Create reports on package downloads Write createProject Create a new project Write createPullRequest Create a new pull request Write createRepository Create a new repository Write createWorkItem Create a new work item Write manageContainerPolicies Manage policies for container repositories Write manageSecurityPolicies Manage security policies Write manageTestEnvironments Manage test environments for different test types Write manageUniversalPackages Manage universal packages Write mergePullRequest Merge a pull request Write moveCardOnBoard Move a card on a board Write promotePackage Promote a package version between views Write publishPackage Publish a package to a feed Write trackSecurityVulnerabilities Track and manage security vulnerabilities Write updateWorkItem Update an existing work item Write updateWorkItemState Update the state of a work item

DESTRUCTIVE 1 tools

Destructive deletePackageVersion Delete a version of a package

EXECUTE 9 tools

Execute runAutomatedTests Execute automated test suites Execute runComplianceChecks Run compliance checks against standards Execute runSecurityScan Run security scans on repositories Execute runTestImpactAnalysis Determine which tests to run based on code changes Execute runTestOptimization Optimize test suite execution for faster feedback Execute optimizeTestSelection Intelligently select tests to run based on changes Execute rotateSecrets Rotate secrets and credentials Execute vaultIntegration Integrate with secret vaults Execute createTestDataGenerator Generate test data for automated tests

// FAQ

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

The Azure Devops MCP server exposes 97 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Azure Devops tools? +

Route the Azure Devops server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Azure Devops tools fall into? +

Azure Devops tools are categorised as Read (57), Write (30), Destructive (1), Execute (9). Each category has a recommended default policy.

Enforce policy on every Azure Devops tool call.

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

GOVERN AZURE DEVOPS →

Free to start. No card required.

42,500+ MCP servers and 110,000+ tools scanned and risk-classified.