Search for Jira issues using JQL. Supports complex queries with pagination and field selection. Examples: "project = PROJECT AND status = Open", "assignee = currentUser()". For pagination, use nextPageToken from previous response.
AI agents call jira_search_issues to retrieve information from Mcp Jira Stdio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
jql | string | Yes | JQL query string |
expand | array | — | Additional details to include |
fields | array | — | Specific fields to retrieve |
maxResults | number | — | Maximum number of results to return per page |
nextPageToken | string | — | Token for pagination. Omit for first page, use value from previous response for next page. |
Parameters from the server's own tool schema.
This tool performs a search query operation that retrieves and returns Jira issue data without any side effects. It supports pagination and field selection for querying, which are classic read-only operations. The description explicitly indicates searching/querying functionality with no mention of creating, modifying, or deleting data. This falls squarely into the Read category.
From the tool's definition Tool name is 'jira_search_issues' and description states 'Search for Jira issues using JQL' with examples showing query patterns that retrieve data. No modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Search for Jira issues using JQL. Supports complex queries with pagination and field selection. Examples: "project = PROJECT AND status = Open", "assignee = currentUser()". For pagination, use nextPageToken from previous response. It is categorised as a Read tool in the Mcp Jira Stdio MCP Server, which means it retrieves data without modifying state.
jira_search_issues accepts 5 parameters: jql, expand, fields, maxResults, nextPageToken. Required: jql. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_search_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 Jira Stdio. Nothing to install.
jira_search_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 jira_search_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 jira_search_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.
jira_search_issues is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →