Get the code review guidelines.
AI agents call get_review_guidelines to retrieve information from GitLab Code Review MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches static review guidelines from the GitLab server. It performs no modifications, deletions, approvals, or external operations—only data retrieval. The blast radius is minimal as it cannot alter repository state or trigger unintended actions. Even if misused by an AI agent, it would only expose guidelines information without operational consequences.
From the tool's definition The tool name 'get_review_guidelines' and description 'Get the code review guidelines' indicate a retrieval operation with no side effects. The verb 'get' is a read operation that queries and returns existing configuration data.
Attacks that exploit this kind of access
Get the code review guidelines. It is categorised as a Read tool in the GitLab Code Review MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab Code Review MCP server in PolicyLayer and add a rule for get_review_guidelines: 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 Code Review MCP. Nothing to install.
get_review_guidelines 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_guidelines 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_guidelines. 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_guidelines is provided by the GitLab Code Review MCP server (lininn/gitlab-code-review-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_review_guidelines is one line of GitLab Code Review'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 →