AI agents call list_processes to retrieve information from Ado without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'list_processes' is a classic Read pattern—it retrieves information (likely Azure DevOps processes/definitions) without side effects. While the description is empty (reducing confidence slightly), the sibling tool context confirms this server distinguishes between read operations (list/extract/analyze) and destructive/write operations.
From the tool's definition Tool name 'list_processes' indicates querying/listing operations with no modification capability. Description is empty, but sibling tools on this server include destructive operations (delete_pipeline, delete_work_item, delete_work_items_batch) and write…
Attacks that exploit this kind of access
list_processes. It is categorised as a Read tool in the Ado MCP Server, which means it retrieves data without modifying state.
Register the Ado 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 Ado. 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 Ado MCP server (raboley/ado-mcp). 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 →