create_merge_request · CODING DevOps MCP Server MCP

WHAT IT DOES

What create_merge_request does on CODING DevOps MCP Server

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

WHY IT NEEDS A POLICY

Why create_merge_request needs a policy

Creating a merge request is a write operation that initiates a code review workflow. While merge requests represent proposed changes, they are reversible: they can be closed, rejected, or their underlying branches deleted without permanent impact. This distinguishes it from destructive operations.

From the tool's definition Tool name 'create_merge_request' and description state it '创建合并请求' (creates a merge request). Merge requests are reversible modifications to the version control workflow - they can be closed, declined, or reverted without permanent data loss.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_merge_request Rate-limited

create_merge_request 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": {
    "create_merge_request": {
      "limits": [
        {
          "counter": "create_merge_request_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 CODING DevOps MCP Server, so you can run agents against it safely.

FAQ

Questions about create_merge_request

What does the create_merge_request tool do? +

创建合并请求。需要提供工作目录路径，会自动从指定目录的 Git 仓库获取仓库信息。如果不指定源分支，将使用当前分支；如果不指定目标分支，将使用 master。仓库路径会自动从 Git 远程仓库地址中解析。. It is categorised as a Write tool in the CODING DevOps 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 create_merge_request? +

Register the CODING DevOps MCP Server MCP server in PolicyLayer and add a rule for 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 CODING DevOps MCP Server. Nothing to install.

What risk level is create_merge_request? +

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 create_merge_request? +

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

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

create_merge_request is provided by the CODING DevOps MCP Server MCP server (yupengfei1209/coding_devops_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.