Lists all available processes in the organization. Use this tool when you need to: - See what processes are available in your Azure DevOps organization - Find process IDs for project creation or configuration - Check which process is set as the default Returns: A formatted table of all processes ...
AI agents call list_processes to retrieve information from MCP Azure DevOps Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and returns process metadata from Azure DevOps. It retrieves information without creating, modifying, deleting, or executing any operations. No reversible or irreversible changes are made.
From the tool's definition Tool 'lists all available processes' and 'returns a formatted table of all processes' - read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_processes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Azure DevOps Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_processes:
{
"version": "1",
"default": "deny",
"tools": {
"list_processes": {}
}
}list_processes 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.
Lists all available processes in the organization. Use this tool when you need to: - See what processes are available in your Azure DevOps organization - Find process IDs for project creation or configuration - Check which process is set as the default Returns: A formatted table of all processes with names, IDs, and descriptions. It is categorised as a Read tool in the MCP Azure DevOps Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Azure DevOps Server MCP server in PolicyLayer and add a rule for list_processes: 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 MCP Azure DevOps Server. Nothing to install.
list_processes 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_processes 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_processes. 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_processes is provided by the MCP Azure DevOps Server MCP server (vortiago/mcp-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 MCP Azure DevOps Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 MCP Azure DevOps Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.