Get list of supported programming languages for code analysis
AI agents call get_supported_languages to retrieve information from GitLab Review MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static configuration data (supported languages list) with no side effects, read operations, no code execution, and no data modification. It poses minimal risk as it simply provides information about the server's capabilities.
From the tool's definition Tool name 'get_supported_languages' and description 'Get list of supported programming languages for code analysis' indicate a query operation that retrieves metadata without modifying or executing any code.
Attacks that exploit this kind of access
Get list of supported programming languages for code analysis. It is categorised as a Read tool in the GitLab Review MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab Review MCP server in PolicyLayer and add a rule for get_supported_languages: 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 Review MCP. Nothing to install.
get_supported_languages 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_supported_languages 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_supported_languages. 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_supported_languages is provided by the GitLab Review MCP server (lininn/gitlab-review-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 →