get_issue
AI agents call get_issue to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The `get_issue` tool retrieves issue data from Jira without modifying or executing operations. Despite the empty description, the naming pattern and functional context within the Jira/Atlassian MCP server strongly indicate this is a data retrieval operation with no side effects. The blast radius is minimal—it can only expose existing data that the authenticated user has permission to view.
From the tool's definition Tool is named `get_issue` with context of Jira operations; sibling tools like `get_agile_boards`, `get_all_projects`, `get_board_issues`, `get_comments`, and `get_attachments` are all read-only retrieval operations.
Attacks that exploit this kind of access
get_issue. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for 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 MCP Atlassian. Nothing to install.
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 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 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.
get_issue is provided by the MCP Atlassian MCP server (lklkxcxc/mcp-atlassian). 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 →