Create or update a file in a GitLab project
AI agents use create_or_update_file to create or update resources in GitLab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab MCP Server environment.
The tool creates new files or modifies existing ones in a repository, which are classic write operations. It is reversible (files can be edited or deleted later), so it does not qualify as Destructive. However, the severity is high because an AI agent could introduce malicious code, overwrite critical project files, or corrupt the repository's integrity if misused.
From the tool's definition Tool name explicitly states 'create_or_update_file'; description confirms it creates or modifies files in a GitLab project. This is a reversible write operation.
Documented attack patterns abuse exactly the kind of access create_or_update_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_or_update_file:
{
"version": "1",
"default": "deny",
"tools": {
"create_or_update_file": {
"limits": [
{
"counter": "create_or_update_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_or_update_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create or update a file in a GitLab project. It is categorised as a Write tool in the GitLab MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for create_or_update_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 GitLab MCP Server. Nothing to install.
create_or_update_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_or_update_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_or_update_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_or_update_file is provided by the GitLab MCP Server MCP server (radostkali/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitLab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 GitLab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.