mcp_ado_repo_list_branches_by_repo
List all branches in a repository
Part of the Azure DevOps MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call mcp_ado_repo_list_branches_by_repo to retrieve information from Azure DevOps without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON MCP_ADO_REPO_LIST_BRANCHES_BY_REPO
Even though mcp_ado_repo_list_branches_by_repo only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
mcp_ado_repo_list_branches_by_repo:
rules:
- action: allow See the full Azure DevOps policy for all 84 tools.
DETAILS
Tool Name
mcp_ado_repo_list_branches_by_repo
Category
Read
MCP Server
Azure DevOps MCP ServerRisk Level
Low
MORE AZURE DEVOPS TOOLS
mcp_ado_advsec_get_alerts Read mcp_ado_advsec_get_alert_details Read mcp_ado_core_list_projects Read mcp_ado_core_list_project_teams Read mcp_ado_core_get_identity_ids Read mcp_ado_pipelines_get_builds Read mcp_ado_pipelines_get_build_status Read mcp_ado_pipelines_get_build_log Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the mcp_ado_repo_list_branches_by_repo tool do?
List all branches in a repository. It is categorised as a Read tool in the Azure DevOps MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on mcp_ado_repo_list_branches_by_repo?
Add a rule in your Intercept YAML policy under the tools section for mcp_ado_repo_list_branches_by_repo. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Azure DevOps MCP server.
What risk level is mcp_ado_repo_list_branches_by_repo?
mcp_ado_repo_list_branches_by_repo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit mcp_ado_repo_list_branches_by_repo?
Yes. Add a rate_limit block to the mcp_ado_repo_list_branches_by_repo rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
How do I block mcp_ado_repo_list_branches_by_repo completely?
Set action: deny in the Intercept policy for mcp_ado_repo_list_branches_by_repo. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
What MCP server provides mcp_ado_repo_list_branches_by_repo?
mcp_ado_repo_list_branches_by_repo is provided by the Azure DevOps MCP server (@azure-devops/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON AZURE DEVOPS
Open source. One binary. Zero dependencies.