List all projects in the Azure DevOps organization
AI agents call list_projects to retrieve information from Azure DevOps MCP Server for Cline without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation with no side effects. It queries the Azure DevOps organization to return a list of projects. The verb 'list' is explicitly a Read-category action. Even in the context of a sensitive system like Azure DevOps, listing projects is informational only and poses minimal risk unless the organization structure itself is highly sensitive; however, this is typical low-risk enumeration.
From the tool's definition The tool name 'list_projects' and description 'List all projects in the Azure DevOps organization' indicate a read-only operation that retrieves and enumerates existing projects without modifying, executing, or deleting any data.
Documented attack patterns abuse exactly the kind of access list_projects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server for Cline, and nothing reaches the server without passing your rules. This is the rule we recommend for list_projects:
{
"version": "1",
"default": "deny",
"tools": {
"list_projects": {}
}
}list_projects 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 projects in the Azure DevOps organization. It is categorised as a Read tool in the Azure DevOps MCP Server for Cline MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server for Cline MCP server in PolicyLayer and add a rule for list_projects: 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 for Cline. Nothing to install.
list_projects 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_projects 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_projects. 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_projects is provided by the Azure DevOps MCP Server for Cline MCP server (stefanskiasan/azure-devops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Azure DevOps MCP Server for Cline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Azure DevOps MCP Server for Cline tools catalogued and risk-classified — across an index of 42,500+ MCP servers.