gh_issue_close · GitHub CLI MCP Server MCP: Risk & Policy

WHAT IT DOES

What gh_issue_close does on GitHub CLI MCP Server

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

WHY IT NEEDS A POLICY

Why gh_issue_close needs a policy

Closing an issue modifies data state but is reversible—the issue can be reopened. This qualifies as Write rather than Destructive. The severity is medium because an agent closing issues indiscriminately could disrupt project workflows and collaboration, but the impact is not as severe as permanent data loss or financial consequences.

From the tool's definition Tool name 'gh_issue_close' and description 'Close an issue' indicate modification of issue state. Closing an issue changes its status from open to closed, which is a reversible state change (issues can be reopened).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gh_issue_close Rate-limited

gh_issue_close 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": {
    "gh_issue_close": {
      "limits": [
        {
          "counter": "gh_issue_close_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 GitHub CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about gh_issue_close

What does the gh_issue_close tool do? +

Close an issue. It is categorised as a Write tool in the GitHub CLI MCP 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 gh_issue_close? +

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

What risk level is gh_issue_close? +

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

Can I rate-limit gh_issue_close? +

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

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

gh_issue_close is provided by the GitHub CLI MCP Server MCP server (munch-group/gh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.