Displays a hierarchical tree view of files and directories within a single repository starting from an optional path
AI agents call get_repository_tree 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 and presents repository file structure without modifying, deleting, or executing any code. It is a read-only query operation analogous to 'ls' or 'find' commands. The blast radius of misuse is minimal—an agent could map repository structure but cannot alter code, trigger deployments, or access file contents (per sibling tool get_file_content being separate). Classified as Read with low severity.
From the tool's definition Tool displays a hierarchical tree view of files and directories within a repository. Keywords: 'Displays', 'tree view', 'read-only introspection of repository structure'.
Documented attack patterns abuse exactly the kind of access get_repository_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_repository_tree:
{
"version": "1",
"default": "deny",
"tools": {
"get_repository_tree": {}
}
}get_repository_tree 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.
Displays a hierarchical tree view of files and directories within a single repository starting from an optional path. 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_repository_tree: 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_repository_tree 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_repository_tree 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_repository_tree. 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_repository_tree is provided by the Azure DevOps MCP Server MCP server (tiberriver256/mcp-server-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 42 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Azure DevOps MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.