List releases from a CERN GitLab repository.
AI agents call list_releases to retrieve information from CERN GitLab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries release information from a repository without modifying, executing, or deleting any data. It is a straightforward read operation that returns existing release metadata. The low severity reflects minimal blast radius—an agent misusing this tool could only expose or enumerate public release information, which is typically non-sensitive in a collaborative development environment.
From the tool's definition Tool name is 'list_releases' and description states 'List releases from a CERN GitLab repository.' The verb 'list' and the read-only nature of retrieving release information indicates data retrieval with no side effects.
Attacks that exploit this kind of access
List releases from a CERN GitLab repository. It is categorised as a Read tool in the CERN GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CERN GitLab MCP Server MCP server in PolicyLayer and add a rule for list_releases: 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 CERN GitLab MCP Server. Nothing to install.
list_releases 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 list_releases 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 list_releases. 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.
list_releases is provided by the CERN GitLab MCP Server MCP server (mohamedelashri/cerngitlab-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 →