create_release
AI agents use create_release to create or update resources in Qodev Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qodev Gitlab environment.
Creating a release is a reversible Write operation—it creates and publishes a new release version in a GitLab repository, which can be deleted or modified later. While the description is empty, the tool name combined with the server's stated capability to manage 'releases' and the pattern of other write-category tools on this server strongly suggests this creates release artifacts.
From the tool's definition Tool name 'create_release' indicates creation of a release artifact in GitLab. The sibling tools on this server include create_issue, create_merge_request, and merge_merge_request, which are all Write operations.
Attacks that exploit this kind of access
create_release. It is categorised as a Write tool in the Qodev Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qodev Gitlab MCP server in PolicyLayer and add a rule for create_release: 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 Qodev Gitlab. Nothing to install.
create_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_release 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 create_release. 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.
create_release is provided by the Qodev Gitlab MCP server (qodevai/gitlab-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 →