Get full details for a Jira issue by key (e.g., ONE-123).
AI agents call get_issue to retrieve information from Simple Jira MCP 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 existing Jira issue data without creating, modifying, deleting, or executing any operations. It is a standard read operation with minimal risk unless the retrieved data itself is sensitive, but the tool's function is purely informational. Severity is low because misuse would only expose information already accessible to authenticated users within Jira's permission model.
From the tool's definition Tool description states 'Get full details for a Jira issue by key' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get full details for a Jira issue by key (e.g., ONE-123). It is categorised as a Read tool in the Simple Jira MCP MCP Server, which means it retrieves data without modifying state.
Register the Simple Jira 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 Simple Jira MCP. 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 Simple Jira MCP server (timohaa/simple-jira-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 →