github_close_issue

Close an issue.

SERVERGithub SOURCEdkeeno/github-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-close-issue.md

WHAT IT DOES

What github_close_issue does on Github

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

RISK

Why github_close_issue is rated Medium

Closing an issue is a reversible write operation that changes the status of an issue from open to closed. While it modifies data, it is not destructive (the issue and its content remain accessible) and is easily undone by reopening the issue. This places it in the Write category rather than Destructive.

From the tool's definition Tool name is 'github_close_issue' and description states it will 'Close an issue.' Closing an issue modifies the state of an issue resource on GitHub.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_close_issue safely

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

github_close_issue Rate-limited

github_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": {
    "github_close_issue": {
      "limits": [
        {
          "counter": "github_close_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_close_issue

What does the github_close_issue tool do? +

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

How do I enforce a policy on github_close_issue? +

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

What risk level is github_close_issue? +

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

Can I rate-limit github_close_issue? +

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

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

github_close_issue is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 69 Github tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →