Searches for Jira issues using Jira Query Language (JQL). This is the primary way to find issues that match specific criteria.
AI agents call search_jira_issues 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.
This tool queries and retrieves Jira issues based on search criteria. It has no side effects—it does not create, modify, delete, or execute code. It is purely informational and read-only in nature, making it a Read category risk with low severity.
From the tool's definition Tool performs search/query operation using JQL without modifying data. Description states it 'Searches for Jira issues' which is a retrieval operation.
Attacks that exploit this kind of access
Searches for Jira issues using Jira Query Language (JQL). This is the primary way to find issues that match specific criteria. 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 search_jira_issues: 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.
search_jira_issues 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 search_jira_issues 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 search_jira_issues. 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.
search_jira_issues is provided by the Mcp Atlassian MCP server (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 →