get_merge_request_note

What get_merge_request_note does on Gitlab Mcp

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

Why get_merge_request_note is rated Low

This tool retrieves (gets) a specific note associated with a merge request. It is a read-only query operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an AI agent could only access notes that exist, potentially revealing information depending on access controls, but cannot alter state or trigger external operations.

From the tool's definition Tool name 'get_merge_request_note' and description 'Get a specific note for a merge request' indicate a retrieval operation with no modification or side effects.

The rule that runs get_merge_request_note safely

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

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

Questions about get_merge_request_note