# security_scan_profile — gitlab

> 3 actions
> This page as plain markdown. Index: https://mcp.jmrp.io/llms.txt

Canonical: https://mcp.jmrp.io/servers/gitlab/actions/security_scan_profile/
Language: en
Alternate: https://mcp.jmrp.io/es/servers/gitlab/actions/security_scan_profile/index.md
Updated: 2026-11-10T02:24:12+01:00
License: https://mcp.jmrp.io/license/

Counted against gitlab.com, which is the only host this endpoint talks to, with a token it resolves to the Ultimate tier: to use it against a self-managed instance, run the server yourself — its documentation covers that. The catalog is scoped to the token that asks, so the count moves with both its tier and its permissions: a Free token sees fewer actions, a member of a group on a paid plan sees that plan's, and administration domains only appear to tokens allowed to use them. That is why the figures differ elsewhere: the upstream project counts 872 operations on Community Edition and up to 1,099 on GitLab.com's top tier, while this deployment publishes 977 because it is OAuth-only and acts with your token, so the administration domains a non-admin account cannot call never appear. All three describe the same catalog, counted from three vantage points.

Each entry also says what a GitLab fine-grained personal access token needs to run it, as GitLab 19.5.0 declares it: every permission of one line, at one of the boundaries named. Where there are alternatives, any one is enough. What follows "Some calls also need" is needed only by the calls that send that request, and the parts of the answer GitLab serves empty to such a token are listed apart.

## Actions

### `security_scan_profile.attach` — Attach Security Scan Profile

Attach a GitLab security scan profile to one or more projects and/or groups via GraphQL. Requires Ultimate. Returns: attach confirmation with the resolved profile and targets. See also: security_scan_profile.detach, security_scan_profile.list_project_statuses, project.get. API docs: https://docs.gitlab.com/api/graphql/reference/#mutationsecurityscanprofileattach

**Required parameters:** `security_scan_profile_id (string)`

**At least one of:** `project_ids (array)` or `group_ids (array)`

**Fine-grained token:** none can run it at this GitLab release, which declares nothing for it; use a classic token

### `security_scan_profile.detach` — Detach Security Scan Profile

_destructive_

Detach a GitLab security scan profile from one or more projects and/or groups via GraphQL. Requires Ultimate. Returns: detach confirmation with the resolved profile and targets. See also: security_scan_profile.attach, security_scan_profile.list_project_statuses, project.get. API docs: https://docs.gitlab.com/api/graphql/reference/#mutationsecurityscanprofiledetach

**Required parameters:** `security_scan_profile_id (string)`

**At least one of:** `project_ids (array)` or `group_ids (array)`

**Fine-grained token:** none can run it at this GitLab release, which declares nothing for it; use a classic token

### `security_scan_profile.list_project_statuses` — List Project Scan Profile Statuses

_read-only_

List the security scan profile statuses for a GitLab project via GraphQL. Requires Ultimate. Returns: per-scan-type profile status (NOT_CONFIGURED, PENDING, ACTIVE, WARNING, FAILED, or STALE). See also: security_scan_profile.attach, security_scan_profile.detach, project.get. API docs: https://docs.gitlab.com/api/graphql/reference/#project-scanprofilestatuses

**Required parameters:** `project_full_path (string)`

**Fine-grained token:** none can run it at this GitLab release, which declares nothing for it; use a classic token
