AI agents use push_files to create or update resources in Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab environment.
The push_files tool modifies repository state by creating a new commit with file changes. This is a Write operation because: (1) it creates/modifies data (commits and file content), (2) the changes are reversible via git revert/reset, and (3) it does not irreversibly delete data.
From the tool's definition Tool description states 'Push multiple files to a GitLab project in a single commit' — this directly creates/modifies repository content through a commit operation, which is reversible (commits can be reverted).
Documented attack patterns abuse exactly the kind of access push_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for push_files:
{
"version": "1",
"default": "deny",
"tools": {
"push_files": {
"limits": [
{
"counter": "push_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}push_files 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.
Push multiple files to a GitLab project in a single commit. It is categorised as a Write tool in the Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab MCP server in PolicyLayer and add a rule for push_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. Nothing to install.
push_files 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 push_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 push_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.
push_files is provided by the Gitlab MCP server (yoda-digital/mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Gitlab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Gitlab tools catalogued and risk-classified — across an index of 42,500+ MCP servers.