gitlab_list_personal_access_tokens

List YOUR OWN personal access tokens (the user the GITLAB_TOKEN authenticates as).

SERVERGitlab SOURCEdkeeno/gitlab-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-list-personal-access-tokens.md

WHAT IT DOES

What gitlab_list_personal_access_tokens does on Gitlab

AI agents call gitlab_list_personal_access_tokens to retrieve information from Gitlab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why gitlab_list_personal_access_tokens is rated Low

This is a read-only operation that queries and returns a list of the authenticated user's personal access tokens. While it retrieves sensitive credential metadata, it does not execute code, modify data, delete data, or move money.

From the tool's definition Tool name is 'gitlab_list_personal_access_tokens' and description explicitly states 'List YOUR OWN personal access tokens' — a retrieval operation with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitlab_list_personal_access_tokens safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_list_personal_access_tokens, this is the rule to start with:

gitlab_list_personal_access_tokens Allowed

gitlab_list_personal_access_tokens is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitlab_list_personal_access_tokens": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab, apply this rule, and every gitlab_list_personal_access_tokens call is checked against it from then on.

FAQ

Questions about gitlab_list_personal_access_tokens

What does the gitlab_list_personal_access_tokens tool do? +

List YOUR OWN personal access tokens (the user the GITLAB_TOKEN authenticates as). It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gitlab_list_personal_access_tokens? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_list_personal_access_tokens: 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_list_personal_access_tokens? +

gitlab_list_personal_access_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gitlab_list_personal_access_tokens? +

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

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

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

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 56 Gitlab tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →