push_files

Push multiple files in a single commit

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/push-files.md

WHAT IT DOES

What push_files does on Gitlab Mcp

AI agents use push_files to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.

RISK

Why push_files is rated Medium

Pushing files creates new commits and modifies the repository state. This is reversible (commits can be reverted), so it is Write rather than Destructive. It does not execute arbitrary code, delete data irreversibly, or move money. Severity is medium because misuse could introduce unwanted code or data into a repository, but the operation is auditable and can be undone through standard version control practices.

From the tool's definition Tool name is 'push_files' and description states 'Push multiple files in a single commit' — this creates/modifies repository content via a commit operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs push_files safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For push_files, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every push_files call is checked against it from then on.

FAQ

Questions about push_files

What does the push_files tool do? +

Push multiple files in a single commit. It is categorised as a Write tool in the Gitlab Mcp 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 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. 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 (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

scaffold_project_files on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →