Obtenir les details d
AI agents call get_merge_request to retrieve information from Mcp Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves merge request details without modifying, executing, or deleting data. It is a straightforward read operation querying GitLab merge request information. No destructive, financial, or code execution capabilities are present. Low severity due to minimal blast radius—misuse would only expose existing data.
From the tool's definition Tool name 'get_merge_request' combined with server description indicating it 'Provides full control over GitLab...merge requests' in a conversational interface. The 'get' verb and context of retrieving details indicates a read operation without side effects.
Attacks that exploit this kind of access
Obtenir les details d. It is categorised as a Read tool in the Mcp Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for 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 Mcp Gitlab. Nothing to install.
get_merge_request 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 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. 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 is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →