issue-close

Closes an issue with an optional comment and reason. Returns structured data with issue number, state, URL, reason, and comment URL.

SERVERGit SOURCEDave-London/Pare

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/io-github-dave-london-git/issue-close.md

WHAT IT DOES

What issue-close does on Git

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

RISK

Why issue-close is rated Medium

Closing an issue modifies the state of a GitHub issue to 'closed' and optionally adds a comment. This is a write operation because it creates/modifies data reversibly. While it affects project workflow, it is not destructive (the issue remains accessible and can be reopened) and does not delete data.

From the tool's definition Tool description states it 'Closes an issue' which is a state modification operation. This is a reversible change (issues can be reopened) rather than irreversible deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs issue-close safely

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

issue-close Rate-limited

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": {
    "issue-close": {
      "limits": [
        {
          "counter": "issue-close_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 Git, apply this rule, and every issue-close call is checked against it from then on.

FAQ

Questions about issue-close

What does the issue-close tool do? +

Closes an issue with an optional comment and reason. Returns structured data with issue number, state, URL, reason, and comment URL. It is categorised as a Write tool in the Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on issue-close? +

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

What risk level is issue-close? +

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

Can I rate-limit issue-close? +

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

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

issue-close is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

The MCP Attack Database →

Guides

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