Low Risk

gitlab_my_issues

List issues assigned to the current authenticated user.

How to control gitlab_my_issues ↓

What gitlab_my_issues does on Gitlab

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

Low Risk

Why gitlab_my_issues needs a policy

This tool retrieves and queries existing data (issues) without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, matching the 'Read' category definition of retrieving or querying data with no side effects.

From the tool's definition Tool description states 'List issues assigned to the current authenticated user' - a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access gitlab_my_issues gives an agent:

How to control gitlab_my_issues

PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_my_issues:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitlab_my_issues": {}
  }
}

gitlab_my_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Gitlab — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about gitlab_my_issues

What does the gitlab_my_issues tool do? +

List issues assigned to the current authenticated user. 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_my_issues? +

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

What risk level is gitlab_my_issues? +

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

Can I rate-limit gitlab_my_issues? +

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

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

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

Enforce policy on every Gitlab tool call.

Start from Gitlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.