Search for JIRA issues using JQL (JIRA Query Language). Returns a list of issues matching the query.
AI agents call jira_search to retrieve information from JIRA 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 JIRA issue data without creating, modifying, or deleting anything. It is a read-only operation that returns search results. The JQL (JIRA Query Language) query is used for filtering and searching, not for executing arbitrary code or performing destructive operations.
From the tool's definition Tool description explicitly states it 'Search[es] for JIRA issues' and 'Returns a list of issues matching the query.' The name 'jira_search' and the action of querying with JQL to retrieve results indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search for JIRA issues using JQL (JIRA Query Language). Returns a list of issues matching the query. It is categorised as a Read tool in the JIRA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for jira_search: 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 MCP Server. Nothing to install.
jira_search 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 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. 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 is provided by the JIRA MCP Server MCP server (longmaba/jira-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 →