gitlab_create_release

THE RISK

Medium Risk

Why gitlab_create_release needs a policy

Creating a release is a write operation that produces a new, tagged version of a project with associated artifacts and metadata. This is reversible (the release can be deleted) but represents a significant project state change with potential downstream effects on users, CI/CD pipelines, and deployments.

From the tool's definition Tool name 'gitlab_create_release' and description 'Create a release' indicate creation of a new release artifact in GitLab.

Documented attack patterns abuse exactly the kind of access gitlab_create_release gives an agent:

POLICY

How to control gitlab_create_release

PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_create_release:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitlab_create_release": {
      "limits": [
        {
          "counter": "gitlab_create_release_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

gitlab_create_release stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Gitlab — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Gitlab tools

Destructive gitlab_delete_branch Delete a repository branch permanently. Requires branch. Recommended pre-check: gitlab_get Destructive gitlab_delete_draft_note Delete a merge-request draft note permanently. Irreversible. Requires merge_request_iid an Destructive gitlab_delete_group_wiki_page Delete a group wiki page permanently. Irreversible. Requires group_id and slug. Recommende Destructive gitlab_delete_issue Delete an issue permanently. Irreversible. Requires issue_iid. Recommended pre-check: gitl Destructive gitlab_delete_issue_emoji_reaction Delete an emoji reaction from an issue permanently. Irreversible for that reaction. Requir Destructive gitlab_delete_issue_link Delete an issue link permanently. Irreversible for that relation. Requires issue_iid and i Destructive gitlab_delete_issue_note_emoji_reaction Delete an emoji reaction from an issue note permanently. Irreversible for that reaction. R Destructive gitlab_delete_label Delete a label permanently. Irreversible. Requires name or label_id. Recommended pre-check

All 190 Gitlab tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gitlab_create_release

What does the gitlab_create_release tool do? +

Create a release. It is categorised as a Write tool in the Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gitlab_create_release? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_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 Gitlab. Nothing to install.

What risk level is gitlab_create_release? +

gitlab_create_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gitlab_create_release? +

Yes. Add a rate_limit block to the gitlab_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.

How do I block gitlab_create_release completely? +

Set action: deny in the PolicyLayer policy for gitlab_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.

What MCP server provides gitlab_create_release? +

gitlab_create_release is provided by the Gitlab MCP server (mcpland/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gitlab tool call.

Start from Gitlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →