# get_issue

Get details of a specific issue

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

## Facts

- Tool: `get_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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why get_issue is rated Low

This tool retrieves information about a Jira issue without creating, modifying, or deleting any data. It is a read-only operation that queries existing data, making it a Read category tool with low severity since the blast radius of misuse is limited to unauthorized information disclosure rather than data manipulation or destruction.

From the tool's own definition: "Tool name 'get_issue' and description 'Get details of a specific issue' indicate data retrieval with no modification or deletion."

## Use case

AI agents call get_issue to retrieve information from Mcp Jira without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_issue": {}
  }
}
```

## Other tools on Mcp Jira (5)

- `delete_issue` — Destructive — https://policylayer.com/tools/1broseidon-mcp-jira-server/delete-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