# delete_issue

Delete a Jira issue

Agent View of the PolicyLayer registry record for `delete_issue`. HTML page: https://policylayer.com/tools/1broseidon-mcp-jira-server/delete-issue

## Facts

- Tool: `delete_issue`
- Server: Mcp Jira (`1broseidon/mcp-jira-server`) — https://policylayer.com/tools/1broseidon-mcp-jira-server.md
- Homepage: https://github.com/1broseidon/mcp-jira-server
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_issue",
    "arguments": {}
  }
}
```

## Why delete_issue is rated Critical

Deleting a Jira issue is irreversible and removes project data that cannot be recovered through normal means. This qualifies as Destructive rather than Write. Severity is high because accidental deletion could disrupt project tracking and workflows, affecting multiple team members relying on issue history. Confidence is very high given the unambiguous language.

From the tool's own definition: "Tool name is 'delete_issue' with description 'Delete a Jira issue'. The verb 'delete' explicitly indicates irreversible removal of data."

## Use case

AI agents call delete_issue to permanently remove resources in Mcp Jira, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Jira:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_issue"
  ]
}
```

## Other tools on Mcp Jira (5)

- `get_issue` — Read — https://policylayer.com/tools/1broseidon-mcp-jira-server/get-issue.md
- `list_issues` — Read — https://policylayer.com/tools/1broseidon-mcp-jira-server/list-issues.md
- `add_comment` — Write — https://policylayer.com/tools/1broseidon-mcp-jira-server/add-comment.md
- `create_issue` — Write — https://policylayer.com/tools/1broseidon-mcp-jira-server/create-issue.md
- `update_issue` — Write — https://policylayer.com/tools/1broseidon-mcp-jira-server/update-issue.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=1broseidon-mcp-jira-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1broseidon-mcp-jira-server