Lists all Git repositories in the configured project.
AI agents call git.repos to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about existing Git repositories without creating, modifying, deleting, or executing any operations. It is a standard enumeration endpoint that returns information only. The blast radius of misuse is minimal—an attacker could discover repository names and structure, but cannot modify or delete repositories or their contents.
From the tool's definition Tool name 'git.repos' and description 'Lists all Git repositories in the configured project' indicate a retrieval operation with no side effects. The verb 'Lists' is explicitly a read operation.
Attacks that exploit this kind of access
Lists all Git repositories in the configured project. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for git.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 Azure DevOps MCP Server. Nothing to install.
git.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 git.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 git.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.
git.repos is provided by the Azure DevOps MCP Server MCP server (varnierg/mcp-for-azure-devops). 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 →