push_files · GitLab MCP Server MCP: Risk & Policy

WHAT IT DOES

What push_files does on GitLab MCP Server

AI agents use push_files 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.

WHY IT NEEDS A POLICY

Why push_files needs a policy

This tool modifies repository data by writing files and creating commits. While it changes code/data in the repository, it is reversible through subsequent commits or revert operations, making it Write rather than Destructive. Severity is high because an AI agent could push malicious code, overwrite critical files, or corrupt project history.

From the tool's definition Tool description states 'Push multiple files to a GitLab project in a single commit' and is part of a server enabling 'file operations, branch management' on GitLab repositories. The action creates/modifies repository content through a commit.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_files Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "push_files": {
      "limits": [
        {
          "counter": "push_files_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitLab MCP Server, so you can run agents against it safely.

FAQ

Questions about push_files

What does the push_files tool do? +

Push multiple files to a GitLab project in a single commit. 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.

How do I enforce a policy on push_files? +

Register the GitLab MCP Server 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 MCP Server. Nothing to install.

What risk level is push_files? +

push_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit push_files? +

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.

How do I block push_files completely? +

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.

What MCP server provides push_files? +

push_files is provided by the GitLab MCP Server MCP server (maxkulish/gitlab-mcp-archive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.