get_my_issues

Gets my GitLab issues. State can be: opened, closed, all

SERVERGitLab MCP Server SOURCEahmedbhl/mcp-server-gitlab

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/ahmedbhl-mcp-server-gitlab/get-my-issues.md

WHAT IT DOES

What get_my_issues does on GitLab MCP Server

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

RISK

Why get_my_issues is rated Low

This tool retrieves issue data from GitLab without creating, modifying, or deleting any resources. It is purely a query/fetch operation that returns information the authenticated user already has permission to access. The blast radius of misuse is minimal—an agent could only read the user's own issues. Classified as Read with low severity.

From the tool's definition Tool name 'get_my_issues' and description 'Gets my GitLab issues' indicates data retrieval with no modification. The state parameter (opened, closed, all) only filters existing data without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_my_issues safely

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

get_my_issues Allowed

get_my_issues 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": {
    "get_my_issues": {}
  }
}

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

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

FAQ

Questions about get_my_issues

What does the get_my_issues tool do? +

Gets my GitLab issues. State can be: opened, closed, all. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_my_issues? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for get_my_issues: 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 get_my_issues? +

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

Can I rate-limit get_my_issues? +

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

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

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

KEEP EXPLORING

More on GitLab MCP Server, and thousands of servers like it.

This server

All 19 GitLab MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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