// MCP TOOL REFERENCE

GITLAB MCP FOR CODE REVIEW TOOLS

8 tools from the GitLab MCP for Code Review MCP Server, categorised by risk level.

View the GitLab MCP for Code Review policy →
// ALL 8 GITLAB MCP FOR CODE REVIEW TOOLS
READ 5 tools
Read compare_versions compare_versions Read fetch_commit_diff fetch_commit_diff Read fetch_merge_request Fetch a GitLab merge request and its contents. Read fetch_merge_request_diff fetch_merge_request_diff Read get_project_merge_requests get_project_merge_requests
WRITE 3 tools
Write add_merge_request_comment add_merge_request_comment Write approve_merge_request approve_merge_request Write unapprove_merge_request Unapprove a merge request.

Route GitLab MCP for Code Review through PolicyLayer and every one of its 8 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the GitLab MCP for Code Review MCP server have? +

The GitLab MCP for Code Review MCP server exposes 8 tools across 2 categories: Read, Write.

How do I enforce policies on GitLab MCP for Code Review tools? +

Route the GitLab MCP for Code Review server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do GitLab MCP for Code Review tools fall into? +

GitLab MCP for Code Review tools are categorised as Read (5), Write (3). Each category has a recommended default policy.

Enforce policy on every GitLab MCP for Code Review tool call.

Start from GitLab MCP for Code Review, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.