glab_issues · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What glab_issues does on RedisNexus

AI agents use glab_issues to create or update resources in RedisNexus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RedisNexus environment.

WHY IT NEEDS A POLICY

Why glab_issues needs a policy

The tool performs reversible modifications to GitLab issues including creating new issues, changing issue status (close/reopen), and adding comments. These are classic Write operations—they alter data but can be undone (issues can be reopened, comments deleted, etc.).

From the tool's definition Tool description states 'create, close, reopen, comment' which are write operations that modify issue state and content. While 'list' and 'view' are read operations, the primary functions are write actions that reversibly change GitLab issue data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

glab_issues Rate-limited

glab_issues stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "glab_issues": {
      "limits": [
        {
          "counter": "glab_issues_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RedisNexus, so you can run agents against it safely.

FAQ

Questions about glab_issues

What does the glab_issues tool do? +

Manage GitLab issues: list, view, create, close, reopen, comment. It is categorised as a Write tool in the RedisNexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on glab_issues? +

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

What risk level is glab_issues? +

glab_issues is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit glab_issues? +

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

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

glab_issues is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.