Upload a file to a project so it can be embedded in an issue, MR, or epic description. Returns the Markdown snippet GitLab expects (e.g. ). Provide exactly one of file_path (read from local disk) or file_base64 (inline data). dry_run=true by default.
AI agents use upload_file to create or update resources in Mcp Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gitlab environment.
This is a Write operation because it creates new data (file upload) in a reversible manner. The upload persists in GitLab's storage system but can be deleted or replaced. It is not Destructive because uploads are not irreversible deletions. It is not Execute because it does not run code or trigger external operations—it simply stores a file.
From the tool's definition Tool uploads a file to a project, creating a new resource in GitLab. Description states it 'Upload a file to a project' and 'Returns the Markdown snippet GitLab expects', indicating persistent storage of data.
Attacks that exploit this kind of access
Upload a file to a project so it can be embedded in an issue, MR, or epic description. Returns the Markdown snippet GitLab expects (e.g. ). Provide exactly one of file_path (read from local disk) or file_base64 (inline data). dry_run=true by default. It is categorised as a Write tool in the Mcp Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for upload_file: 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 Mcp Gitlab. Nothing to install.
upload_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upload_file 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 upload_file. 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.
upload_file is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). 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 →