AI agents call jira_get_issue to retrieve information from Mcp Jira 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 Jira issue data by key without side effects. It is a standard read operation that returns metadata about an existing issue. No data is created, modified, deleted, or financially committed. The blast radius of misuse is limited to information disclosure of potentially sensitive Jira issue details, which is a low-severity risk.
From the tool's definition Tool name 'jira_get_issue' and description 'Get full details of a Jira issue by its key...Returns summary, status, assignee, description, priority, labels and more' indicates retrieval of issue data with no modification or deletion.
Attacks that exploit this kind of access
Get full details of a Jira issue by its key (e.g. PROJ-123). Returns summary, status, assignee, description, priority, labels and more. It is categorised as a Read tool in the Mcp Jira MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jira 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 Mcp Jira. 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 Mcp Jira MCP server (renan1fps/mcp-jira). 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 →