取得 Merge Request 包含的 commits
AI agents call get_merge_request_commits to retrieve information from GitLab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves commit information associated with a merge request. It performs a read-only operation against the GitLab API, returning data without creating, modifying, deleting, or executing any actions. No reversible or irreversible changes occur, and no external code execution is triggered. This is a straightforward data retrieval operation with minimal security impact if misused.
From the tool's definition Tool name 'get_merge_request_commits' and description '取得 Merge Request 包含的 commits' (retrieve commits contained in a Merge Request) indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
取得 Merge Request 包含的 commits. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for get_merge_request_commits: 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 Server. Nothing to install.
get_merge_request_commits is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_merge_request_commits 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.
Set action: deny in the PolicyLayer policy for get_merge_request_commits. 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.
get_merge_request_commits is provided by the GitLab MCP Server MCP server (snowild/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_merge_request_commits is one line of GitLab MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →