Lists all Git repositories in a project
AI agents call git_list_repositories to retrieve information from Azure DevOps Multi-Organization MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries repository metadata without creating, modifying, executing, or deleting anything. It is a straightforward enumeration operation with minimal blast radius if misused by an AI agent (exposure of repository names and structure).
From the tool's definition Tool name is 'git_list_repositories' and description states it 'Lists all Git repositories in a project' — a read-only retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Lists all Git repositories in a project. It is categorised as a Read tool in the Azure DevOps Multi-Organization MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps Multi-Organization MCP Server MCP server in PolicyLayer and add a rule for git_list_repositories: 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 Azure DevOps Multi-Organization MCP Server. Nothing to install.
git_list_repositories 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 git_list_repositories 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 git_list_repositories. 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.
git_list_repositories is provided by the Azure DevOps Multi-Organization MCP Server MCP server (nikydobrev/mcp-server-azure-devops-multi). 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 →