New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gitlab_create_merge_request

Create a new merge request

SERVERSage MCP SOURCEsagemcp/sagemcp
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/sagemcp-sagemcp/gitlab-create-merge-request.md

What gitlab_create_merge_request does on Sage MCP

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

Why gitlab_create_merge_request is rated Medium

This tool creates a new merge request, which is a reversible modification to a GitLab repository's state. While not destructive (can be undone), it has higher severity than a simple Read operation because it modifies repository metadata and workflow state, potentially triggering CI/CD pipelines, notifications, and affecting team collaboration processes.

From the tool's definition Tool name 'gitlab_create_merge_request' and description 'Create a new merge request' indicate the tool creates a new entity (merge request) in GitLab, which is a reversible Write operation.

Questions about gitlab_create_merge_request

What does the gitlab_create_merge_request tool do? +

Create a new merge request. It is categorised as a Write tool in the Sage 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 gitlab_create_merge_request? +

Register the Sage MCP server in PolicyLayer and add a rule for gitlab_create_merge_request: 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 Sage MCP. Nothing to install.

What risk level is gitlab_create_merge_request? +

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

Can I rate-limit gitlab_create_merge_request? +

Yes. Add a rate_limit block to the gitlab_create_merge_request 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 gitlab_create_merge_request completely? +

Set action: deny in the PolicyLayer policy for gitlab_create_merge_request. 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 gitlab_create_merge_request? +

gitlab_create_merge_request is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.