List all repositories in the project
AI agents call list_repos to retrieve information from MCP Server for Azure DevOps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns repository metadata without creating, modifying, deleting, or executing anything. It is a standard read/list operation that retrieves information about available repositories. The blast radius if misused is minimal—an agent could enumerate repositories but cannot alter code, trigger builds, or access sensitive content beyond what the credentials already permit.
From the tool's definition Tool name 'list_repos' and description 'List all repositories in the project' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all repositories in the project. It is categorised as a Read tool in the MCP Server for Azure DevOps MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Azure DevOps MCP server in PolicyLayer and add a rule for list_repos: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP Server for Azure DevOps. Nothing to install.
list_repos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_repos rule in your PolicyLayer 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.
Set action: deny in the PolicyLayer policy for list_repos. 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.
list_repos is provided by the MCP Server for Azure DevOps MCP server (sepal7/mcp-ado). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →