Fetch all Azure DevOps projects in the organization
AI agents call get_projects 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 retrieves project metadata from Azure DevOps without creating, modifying, deleting, or executing any operations. It is a straightforward query operation that returns organization structure data. The blast radius is low since the only risk is information disclosure of project names and basic project information that is typically accessible to organization members.
From the tool's definition Tool name 'get_projects' and description 'Fetch all Azure DevOps projects in the organization' indicate a retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
Fetch all Azure DevOps projects in the organization. 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 get_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. Nothing to install.
get_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 get_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 get_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.
get_projects is provided by the Azure DevOps MCP Server MCP server (saktheeswar/azure_devops_mcp_server). 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 →