Create a new file in a repository. Rejects if the file already exists. dry_run=true by default.
AI agents use create_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.
Creating a file in a repository is a Write operation—it creates data that can be modified or deleted later. It is not Destructive since files can be removed, not Read since it modifies state, and not Execute since it doesn't run code or scripts. Severity is medium because creating files could affect CI/CD pipelines or application logic if placed strategically, but the dry-run default mitigates risk.
From the tool's definition Tool description states 'Create a new file in a repository' and provides dry-run safety via dry_run=true by default. The action creates new data reversibly.
Attacks that exploit this kind of access
Create a new file in a repository. Rejects if the file already exists. 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 create_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.
create_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 create_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 create_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.
create_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 →