AI agents call get_jira_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 tool name strongly suggests a retrieval operation ('get_') for Jira issue data. No description is provided, but the naming convention and parallel structure with other 'get_' tools on the server (get_confluence_content, get_confluence_pages, etc.) indicates this is a read-only operation that queries and returns issue information.
From the tool's definition Tool name 'get_jira_issue' indicates retrieval of issue data. Context from sibling tools shows this server includes both read operations (get_confluence_content, get_confluence_pages, jira_add_comment for reading) and write operations (confluence_create_page,…
Documented attack patterns abuse exactly the kind of access get_jira_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for get_jira_issue:
{
"version": "1",
"default": "deny",
"tools": {
"get_jira_issue": {}
}
}get_jira_issue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_jira_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_jira_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_jira_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_jira_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_jira_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_jira_issue is provided by the MCP Atlassian MCP server (samwang0723/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 MCP Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.