List all Git repositories in an Azure DevOps project. Returns repository details including ID, name, project info, default branch, size, and URLs. Supports both project-specific and organization-wide repository listing. Results are automatically truncated if they exceed size limits.
AI agents call azure_devops_repositories to retrieve information from Cursor Azure Devops 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 modifying, executing, or destructing any data. It is purely informational, listing repositories and their properties within an Azure DevOps project. The low severity reflects minimal blast radius—an AI agent using this tool can only view repository information, posing no direct risk to system integrity or data safety.
From the tool's definition Tool description states it 'List all Git repositories' and 'Returns repository details including ID, name, project info, default branch, size, and URLs.' The verb 'list' and the focus on retrieval with no modification or deletion verbs indicate a read-only…
Documented attack patterns abuse exactly the kind of access azure_devops_repositories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cursor Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for azure_devops_repositories:
{
"version": "1",
"default": "deny",
"tools": {
"azure_devops_repositories": {}
}
}azure_devops_repositories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Git repositories in an Azure DevOps project. Returns repository details including ID, name, project info, default branch, size, and URLs. Supports both project-specific and organization-wide repository listing. Results are automatically truncated if they exceed size limits. It is categorised as a Read tool in the Cursor Azure Devops MCP Server, which means it retrieves data without modifying state.
Register the Cursor Azure Devops MCP server in PolicyLayer and add a rule for azure_devops_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 Cursor Azure Devops. Nothing to install.
azure_devops_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 azure_devops_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 azure_devops_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.
azure_devops_repositories is provided by the Cursor Azure Devops MCP server (maximtitovich/cursor-azure-devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cursor Azure Devops, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Cursor Azure Devops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.