Search issues using JQL (Jira Query Language)
AI agents call jira_search to retrieve information from Jira MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only data retrieval using JQL search syntax. It queries existing Jira issues without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could potentially retrieve sensitive issue information if access controls are weak, but cannot alter system state or trigger external actions. This classifies as a Read operation with low severity.
From the tool's definition Tool description states 'Search issues using JQL' with no mention of modification, deletion, or execution capabilities. The operation is purely query-based retrieval.
Attacks that exploit this kind of access
Search issues using JQL (Jira Query Language). It is categorised as a Read tool in the Jira MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Integration 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 Integration. 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 Integration MCP server (koveh/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 →