create_merge_request_thread

Create a new thread on a merge request

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/create-merge-request-thread.md

What create_merge_request_thread does on Gitlab Mcp

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

Why create_merge_request_thread is rated Medium

This tool creates a new collaborative discussion thread on a merge request, which is a reversible write operation that modifies the merge request's discussion state. It does not execute code, delete data, move money, or trigger external operations—it simply adds a new thread/comment artifact to the MR.

From the tool's definition Tool name explicitly states 'create_merge_request_thread' and description states 'Create a new thread on a merge request', indicating creation of new comment/discussion data on an MR.

Questions about create_merge_request_thread

What does the create_merge_request_thread tool do? +

Create a new thread on a merge request. 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 create_merge_request_thread? +

Register the Gitlab MCP server in PolicyLayer and add a rule for create_merge_request_thread: 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 create_merge_request_thread? +

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

Can I rate-limit create_merge_request_thread? +

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

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

create_merge_request_thread 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.

More on Gitlab, 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 Gitlab'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.