GitLab MRの未解決の指摘事項（コメント）を取得
AI agents call get_review_comments to retrieve information from Https://github Com/owayo/gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing data (review comments) from GitLab merge requests without modifying, deleting, or executing any actions. It is purely informational and has no side effects. The sibling tools (get_pipeline_failed_jobs, get_review_changes) also appear to be read operations, consistent with this classification.
From the tool's definition Tool description states 'GitLab MRの未解決の指摘事項（コメント）を取得' (retrieves unresolved comments on GitLab merge requests). The verb 'to get/retrieve' and the context of fetching review comments indicates a read-only query operation.
Attacks that exploit this kind of access
GitLab MRの未解決の指摘事項（コメント）を取得. It is categorised as a Read tool in the Https://github Com/owayo/gitlab MCP Server, which means it retrieves data without modifying state.
Register the Https://github Com/owayo/gitlab MCP server in PolicyLayer and add a rule for get_review_comments: 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 Https://github Com/owayo/gitlab. Nothing to install.
get_review_comments 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_review_comments 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_review_comments. 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_review_comments is provided by the Https://github Com/owayo/gitlab MCP server (owayo/gitlab-mcp-server). 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 →