# create_issue

Creates a new issue in a project. Labels should be comma-separated

Agent View of the PolicyLayer registry record for `create_issue`. HTML page: https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/create-issue

## Facts

- Tool: `create_issue`
- Server: GitLab MCP Server (`ahmedbhl/mcp-server-gitlab`) — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab.md
- Homepage: https://github.com/ahmedbhl/mcp-server-gitlab
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_issue",
    "arguments": {}
  }
}
```

## Why create_issue is rated Medium

This tool creates new data (an issue) in a reversible manner—issues can be edited, closed, or deleted later. It does not execute arbitrary code, destroy data irreversibly, or move money. It falls squarely within the Write category.

From the tool's own definition: "Tool name 'create_issue' and description 'Creates a new issue in a project' indicate the tool adds new data to a GitLab project."

## Use case

AI agents use create_issue to create or update resources in GitLab MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab MCP Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GitLab MCP Server:

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

## Other tools on GitLab MCP Server (18)

- `compare_branches` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/compare-branches.md
- `get_commit_details` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-commit-details.md
- `get_commit_diff` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-commit-diff.md
- `get_file_content` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-file-content.md
- `get_file_history` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-file-history.md
- `get_my_issues` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-my-issues.md
- `get_my_merge_requests` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-my-merge-requests.md
- `get_my_projects` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-my-projects.md
- `get_project_branches` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-project-branches.md
- `get_project_commits` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-project-commits.md
- `get_project_files` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-project-files.md
- `get_project_info` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-project-info.md
- `get_project_issues` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-project-issues.md
- `get_project_merge_requests` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-project-merge-requests.md
- `get_project_pipelines` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-project-pipelines.md
- `get_user_info` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/get-user-info.md
- `search_files_in_project` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/search-files-in-project.md
- `search_projects` — Read — https://policylayer.com/tools/ahmedbhl-mcp-server-gitlab/search-projects.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ahmedbhl-mcp-server-gitlab · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ahmedbhl-mcp-server-gitlab