create_issue

THE RISK

Medium Risk

Why create_issue needs a policy

This tool creates new issue records in GitLab, which is a reversible write operation. While it modifies project state, issues are not irreversibly destructive data—they can be managed, closed, or removed.

From the tool's definition Tool name 'create_issue' and description 'Create a new issue in a GitLab project' indicate creation of new data in GitLab. This is a write operation that creates a reversible resource (issues can be closed, deleted, or modified).

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

POLICY

How to control create_issue

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

policy.json

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

create_issue 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 MCP Server — 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 MCP Server tools

Write create_merge_request Create a new merge request in a GitLab project Write create_merge_request_line_comment create_merge_request_line_comment Write create_or_update_file Create or update a file in a GitLab project Write create_repository Create a new GitLab project Read get_file_contents Get the contents of a file from a GitLab project Read get_merge_request_diff Get the diff of a merge request to find valid line positions for comments. Read search_repositories Search for GitLab projects

All 8 GitLab MCP Server 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 create_issue

What does the create_issue tool do? +

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

How do I enforce a policy on create_issue? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for create_issue: 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 MCP Server. Nothing to install.

What risk level is create_issue? +

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

Can I rate-limit create_issue? +

Yes. Add a rate_limit block to the create_issue 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 create_issue completely? +

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

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

Enforce policy on every GitLab MCP Server tool call.

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

CHECK YOUR STACK →