AI agents call list_all_projects_with_metadata 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.
This tool retrieves project metadata from Azure DevOps without modifying, deleting, or executing any operations. It is a straightforward read/query operation. Low severity because listing projects provides information that is typically already visible to authenticated users and does not have a blast radius of harm if an AI agent calls it.
From the tool's definition Tool name 'list_all_projects_with_metadata' indicates retrieval of project information with no modification or execution capability. The server description confirms it 'enables them to list projects' as a core read operation.
Attacks that exploit this kind of access
list_all_projects_with_metadata. 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_all_projects_with_metadata: 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_all_projects_with_metadata 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_all_projects_with_metadata 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_all_projects_with_metadata. 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_all_projects_with_metadata 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 →