get_merge_request
Retrieves detailed information about a merge request
Part of the GitLab MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call get_merge_request to retrieve information from GitLab without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON GET_MERGE_REQUEST
Even though get_merge_request only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_merge_request:
rules:
- action: allowSee the full GitLab policy for all 15 tools.
DETAILS
MORE GITLAB TOOLS
get_issue Read get_mcp_server_version Read get_merge_request_commits Read get_merge_request_diffs Read get_merge_request_pipelines Read get_pipeline_jobs Read get_workitem_notes Read gitlab_search Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the get_merge_request tool do?
Retrieves detailed information about a merge request. It is categorised as a Read tool in the GitLab MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on get_merge_request?
Add a rule in your Intercept YAML policy under the tools section for get_merge_request. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the GitLab MCP server.
What risk level is get_merge_request?
get_merge_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit get_merge_request?
Yes. Add a rate_limit block to the get_merge_request rule in your Intercept 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 get_merge_request completely?
Set action: deny in the Intercept policy for 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 get_merge_request?
get_merge_request is provided by the GitLab MCP server (gitlab-org/gitlab-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON GITLAB
Open source. One binary. Zero dependencies.