close_issue · Kepler MCP GitLab Server MCP: Risk & Policy

WHAT IT DOES

What close_issue does on Kepler MCP GitLab Server

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

WHY IT NEEDS A POLICY

Why close_issue needs a policy

Closing an issue modifies its state reversibly (can be reopened), making this a Write operation rather than Destructive. The blast radius is medium because an AI agent could close critical issues incorrectly, disrupting workflows, but the action is reversible. Confidence is 0.85 rather than higher because the tool description is empty, though the name and server context provide strong inferential evidence.

From the tool's definition Tool name 'close_issue' indicates modification of issue state. GitLab context confirms this server manages issues and their lifecycle. The sibling tools (create_issue, add_issue_comment, create_merge_request) confirm write-capable operations on issue objects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_issue Rate-limited

close_issue 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": {
    "close_issue": {
      "limits": [
        {
          "counter": "close_issue_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 Kepler MCP GitLab Server, so you can run agents against it safely.

FAQ

Questions about close_issue

What does the close_issue tool do? +

close_issue. It is categorised as a Write tool in the Kepler MCP GitLab Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_issue? +

Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for close_issue: 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 Kepler MCP GitLab Server. Nothing to install.

What risk level is close_issue? +

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

Can I rate-limit close_issue? +

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

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

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