Get details of a specific Jira issue
AI agents call jira_get_issue to retrieve information from Jira & Confluence 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 and queries issue metadata from Jira. It has no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is minimal; an unauthorized agent could only view issue details it already has access to through the API. Classification as Read is appropriate.
From the tool's definition Tool name 'jira_get_issue' and description 'Get details of a specific Jira issue' indicate retrieval of existing data with no modification, creation, deletion, or execution.
Attacks that exploit this kind of access
Get details of a specific Jira issue. It is categorised as a Read tool in the Jira & Confluence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira & Confluence MCP Server 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 Jira & Confluence MCP Server. 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 Jira & Confluence MCP Server MCP server (katsuhirohonda/jira-confluence-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 →