Get details of a JIRA ticket by key
AI agents call get_jira_ticket to retrieve information from Atlassian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a JIRA ticket without creating, modifying, deleting, or executing any operations. It is a standard read operation that queries existing data. The severity is low because misuse would only expose information already accessible to authenticated users in JIRA, with no destructive or financial consequences.
From the tool's definition Tool description states 'Get details of a JIRA ticket by key' — a retrieval operation with no modification or deletion. The verb 'Get' combined with 'details' indicates a read-only query operation.
Attacks that exploit this kind of access
Get details of a JIRA ticket by key. It is categorised as a Read tool in the Atlassian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP Server MCP server in PolicyLayer and add a rule for get_jira_ticket: 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 Atlassian MCP Server. Nothing to install.
get_jira_ticket 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 get_jira_ticket 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 get_jira_ticket. 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.
get_jira_ticket is provided by the Atlassian MCP Server MCP server (kompallik/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →