get_project_files
Gets files and directories in a project path. Use empty path for root directory
This record as markdown: /tools/ahmedbhl-mcp-server-gitlab/get-project-files.md
What get_project_files does on GitLab MCP Server
AI agents call get_project_files to retrieve information from GitLab MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_project_files is rated Low
This tool queries and retrieves the file/directory structure of a GitLab project without creating, modifying, deleting, or executing anything. It is a straightforward read operation with minimal security impact—the blast radius is limited to potential information disclosure about project structure, which is typically accessible to authorized users anyway.
From the tool's definition Tool name 'get_project_files' and description 'Gets files and directories in a project path' indicate a retrieval operation with no modification or side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_project_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitLab MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_project_files, this is the rule to start with:
get_project_files 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 GitLab MCP Server, apply this rule, and every get_project_files call is checked against it from then on.
Questions about get_project_files
Gets files and directories in a project path. Use empty path for root directory. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for get_project_files: 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 GitLab MCP Server. Nothing to install.
get_project_files 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_project_files 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_project_files. 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_project_files is provided by the GitLab MCP Server MCP server (ahmedbhl/mcp-server-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitLab MCP Server, and thousands of servers like it.
This server
Across the catalogue