Search for Jira issues using JQL
AI agents call jira_search_issues to retrieve information from Jira & Confluence 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/queries data from Jira without modifying, deleting, or executing operations. JQL (Jira Query Language) is a standard search mechanism that returns results. Even if an AI agent misuses this tool by crafting overly broad queries, the worst outcome is information disclosure about issues the agent's account can already access, which is a low-impact read operation.
From the tool's definition Tool name is 'jira_search_issues' and description states 'Search for Jira issues using JQL'. The verb 'search' and explicit statement that this searches issues indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Search for Jira issues using JQL. It is categorised as a Read tool in the Jira & Confluence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira & Confluence MCP Server 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 Jira & Confluence MCP Server. 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 Jira & Confluence MCP Server MCP server (katsuhirohonda/jira-confluence-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 →