Search Jira tickets using natural language queries. Supports filtering by project, status, assignee, and labels. Uses Jira REST API v3 /search/jql with JQL (Jira Query Language) and token-based pagination.
AI agents call search_jira to retrieve information from Atlassian 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 data from Jira without side effects. It performs filtering and pagination on existing tickets but does not modify, delete, or execute arbitrary code. The blast radius of misuse is minimal—an agent could retrieve sensitive ticket information but cannot alter state or trigger external operations.
From the tool's definition Tool description explicitly states it "Search[es] Jira tickets" and uses the read-only "/search/jql" endpoint with filtering options (project, status, assignee, labels). No create, update, delete, or execute operations are mentioned.
Attacks that exploit this kind of access
Search Jira tickets using natural language queries. Supports filtering by project, status, assignee, and labels. Uses Jira REST API v3 /search/jql with JQL (Jira Query Language) and token-based pagination. It is categorised as a Read tool in the Atlassian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP Server MCP server in PolicyLayer and add a rule for search_jira: 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 Atlassian MCP Server. Nothing to install.
search_jira 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 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. 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 is provided by the Atlassian MCP Server MCP server (jaigouk/atlassian-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 →