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-pare-test/issue-close.md
What issue-close does on Test
AI agents use issue-close to create or update resources in Test, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Test environment.
Why issue-close is rated Medium
Closing an issue modifies data state reversibly. It is not destructive (the issue is not deleted, just marked closed), not financial, and not Execute (it doesn't run arbitrary code). The medium severity reflects that unauthorized issue closure could disrupt project workflows and communication, but the impact is limited in scope and reversible.
From the tool's definition Tool description states it "Closes an issue with an optional comment and reason" — this is a state-changing operation that modifies issue data (closing it), but the action is reversible (issues can be reopened).
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 Test, 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 Test, 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 Test MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Test 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 Test. 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 Test 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 Test, and thousands of servers like it.
This server
Across the catalogue