This record as markdown: /tools/io-github-kivanccakmak-yaver/gitlab-mr-create.md
What gitlab_mr_create does on Yaver
AI agents use gitlab_mr_create to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
draft | boolean | — | |
title | string | Yes | |
directory | string | — | |
description | string | — | |
sourceBranch | string | — | |
targetBranch | string | — |
Parameters from the server's own tool schema.
Why gitlab_mr_create is rated Medium
Creating a merge request is a write operation that modifies repository metadata and state. It is reversible (MRs can be closed/deleted), so it does not qualify as Destructive. It does not execute arbitrary code or delete data.
From the tool's definition Tool name 'gitlab_mr_create' and description 'Open a GitLab merge request' indicate the tool creates a merge request, which is a reversible write operation that modifies repository state by proposing code changes.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs gitlab_mr_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_mr_create, this is the rule to start with:
gitlab_mr_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every gitlab_mr_create call is checked against it from then on.
Questions about gitlab_mr_create
Open a GitLab merge request. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gitlab_mr_create accepts 6 parameters: draft, title, directory, description, sourceBranch, targetBranch. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for gitlab_mr_create: 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 Yaver. Nothing to install.
gitlab_mr_create 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 gitlab_mr_create 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 gitlab_mr_create. 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.
gitlab_mr_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue