gitlab_get_merge_request

Get details of a specific merge request

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/gitlab-get-merge-request.md

WHAT IT DOES

What gitlab_get_merge_request does on Sage MCP

AI agents call gitlab_get_merge_request to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why gitlab_get_merge_request is rated Low

This tool queries and returns information about a merge request. It performs a retrieval operation with no side effects, no data modification, no code execution, and no destructive capability. The verb 'get' and the read-only nature of fetching merge request details place it squarely in the Read category. Severity is low because misuse only exposes metadata about code changes, not financial or system-level resources.

From the tool's definition Tool name contains 'get' and description states 'Get details of a specific merge request' — retrieves existing data without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitlab_get_merge_request safely

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

gitlab_get_merge_request Allowed

gitlab_get_merge_request is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitlab_get_merge_request": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about gitlab_get_merge_request

What does the gitlab_get_merge_request tool do? +

Get details of a specific merge request. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gitlab_get_merge_request? +

Register the Sage MCP server in PolicyLayer and add a rule for gitlab_get_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_get_merge_request? +

gitlab_get_merge_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gitlab_get_merge_request? +

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

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

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

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →