AI agents call get_projects 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 tool retrieves project information from Azure DevOps. The 'get' verb strongly indicates a read-only query operation with no ability to modify, delete, or execute operations. Even if an AI agent misuses this tool, it can only access project metadata, posing minimal security risk. Low severity due to limited blast radius and no state-changing capabilities.
From the tool's definition Tool name 'get_projects' indicates a retrieval operation. No description provided, but the verb 'get' combined with plural 'projects' suggests querying/listing Azure DevOps projects without side effects.
Documented attack patterns abuse exactly the kind of access get_projects 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 get_projects:
{
"version": "1",
"default": "deny",
"tools": {
"get_projects": {}
}
}get_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.
get_projects. 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 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 MCP Azure DevOps 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 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.