jira_get_issue
Get a single Jira issue by key, including description and comments.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jira-get-issue.md
What jira_get_issue does on UnClick
AI agents call jira_get_issue to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
site | string | Yes | Jira site (e.g. mycompany) |
email | string | Yes | Atlassian account email |
api_token | string | Yes | Atlassian API token |
issue_key | string | Yes | Issue key (e.g. ENG-123) |
Parameters from the server's own tool schema.
Why jira_get_issue is rated Low
This tool retrieves and queries data from Jira (an issue tracking system). It fetches an issue's description and comments by key, which is a read-only operation with no capability to modify, execute, delete, or perform financial actions. The blast radius is minimal—misuse could expose project information but cannot alter system state.
From the tool's definition Tool name 'jira_get_issue' and description 'Get a single Jira issue by key, including description and comments' indicate retrieval of existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs jira_get_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_get_issue, this is the rule to start with:
jira_get_issue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every jira_get_issue call is checked against it from then on.
Questions about jira_get_issue
Get a single Jira issue by key, including description and comments. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
jira_get_issue accepts 4 parameters: site, email, api_token, issue_key. Required: site, email, api_token, issue_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for jira_get_issue: 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 UnClick. Nothing to install.
jira_get_issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the jira_get_issue 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 jira_get_issue. 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.
jira_get_issue is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue