issue-close
Closes an issue with an optional comment and reason. Returns structured data with issue number, state, URL, reason, and comment URL.
This record as markdown: /tools/io-github-dave-london-npm/issue-close.md
What issue-close does on Npm
AI agents use issue-close to create or update resources in Npm, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Npm environment.
Why issue-close is rated Medium
This tool performs an irreversible state change (closing an issue), which is a modification action. While the effect could theoretically be undone by reopening the issue, the primary action is to write/modify issue state. The severity is medium because misuse could disrupt project workflows (spam closing legitimate issues), but the scope is limited to individual issues and the action is reversible.
From the tool's definition Tool explicitly 'Closes an issue with an optional comment' — this modifies state (issue state changes from open to closed) and is reversible (issues can be reopened), and can add comments.
Attacks that exploit this kind of access
The rule that runs issue-close safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Npm, apply this rule, and every issue-close call is checked against it from then on.
Questions about issue-close
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 Npm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Npm 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 Npm. Nothing to install.
issue-close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
issue-close is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Npm, and thousands of servers like it.
This server
Across the catalogue