gitlab_get_repository_tree
Get the repository file/directory tree
This record as markdown: /tools/sagemcp-sagemcp/gitlab-get-repository-tree.md
What gitlab_get_repository_tree does on Sage MCP
AI agents call gitlab_get_repository_tree to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gitlab_get_repository_tree is rated Low
This tool retrieves structural information about a repository (its file tree) with no side effects. It is a non-destructive query operation analogous to 'ls' or 'find'. While it could expose the structure of private repositories if unauthorized, the tool itself performs only read operations.
From the tool's definition Tool name 'gitlab_get_repository_tree' and description 'Get the repository file/directory tree' indicate a query/retrieval operation that lists files and directories without modification, creation, or deletion.
Attacks that exploit this kind of access
The rule that runs gitlab_get_repository_tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_get_repository_tree, this is the rule to start with:
gitlab_get_repository_tree is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every gitlab_get_repository_tree call is checked against it from then on.
Questions about gitlab_get_repository_tree
Get the repository file/directory tree. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for gitlab_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 Sage MCP. Nothing to install.
gitlab_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 gitlab_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 gitlab_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.
gitlab_get_repository_tree is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue