my_issues

List issues assigned to the authenticated user

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

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/io-github-zereight-gitlab-mcp/my-issues.md

WHAT IT DOES

What my_issues does on Gitlab Mcp

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

RISK

Why my_issues is rated Low

This tool retrieves data (issues) for the authenticated user without modifying, deleting, or executing anything. It is a straightforward query operation with minimal risk—viewing one's own assigned issues poses no security threat to the system.

From the tool's definition Tool lists issues assigned to the authenticated user; 'list' is a Read operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs my_issues safely

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

my_issues Allowed

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

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

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

FAQ

Questions about my_issues

What does the my_issues tool do? +

List issues assigned to the authenticated user. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on my_issues? +

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

What risk level is my_issues? +

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

Can I rate-limit my_issues? +

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

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

my_issues is provided by the Gitlab MCP server (@zereight/mcp-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, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

The MCP Attack Database →

Guides

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