Get the contents of a file or directory from a GitLab project
AI agents call get_file_contents to retrieve information from GitLab 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 data from a GitLab repository without modifying, deleting, or executing anything. It is a straightforward read operation analogous to fetching or querying existing content. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes repository contents already accessible to the authenticated user.
From the tool's definition Tool name is 'get_file_contents' and description states it 'Get[s] the contents of a file or directory from a GitLab project' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the contents of a file or directory from a GitLab project. 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_file_contents: 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_file_contents 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_file_contents 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_file_contents. 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_file_contents is provided by the GitLab MCP Server MCP server (martijndormans/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →