list_repository_tree
AI agents call list_repository_tree to retrieve information from Kepler MCP GitLab Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists the directory/file tree of a repository, which is purely a data retrieval operation. It retrieves information about repository contents without modifying, executing, or deleting anything.
From the tool's definition Tool name 'list_repository_tree' indicates listing/retrieving repository structure; no description provided but naming convention and context among GitLab tools (create, approve, delete operations on other tools) establishes this as a retrieval-only operation…
Attacks that exploit this kind of access
list_repository_tree. It is categorised as a Read tool in the Kepler MCP GitLab Server MCP Server, which means it retrieves data without modifying state.
Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for list_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 Kepler MCP GitLab Server. Nothing to install.
list_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 list_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 list_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.
list_repository_tree is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_repository_tree is one line of Kepler MCP GitLab Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →