jira_search_jql_tool
AI agents call jira_search_jql_tool 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.
JQL searches are read-only query operations that retrieve data without modifying, deleting, or executing code. No side effects or state changes occur. The tool fits the 'Read' category as it queries and retrieves issue data. Severity is low because search operations have minimal blast radius even if misused—an AI might retrieve sensitive data, but cannot modify systems or cause irreversible damage.
From the tool's definition Tool name 'jira_search_jql_tool' indicates querying/searching via JQL (Jira Query Language); sibling tools include 'jira_filter_execute_tool' and 'jira_comment_list_tool' which are read operations, establishing the pattern.
Attacks that exploit this kind of access
jira_search_jql_tool. 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_jql_tool: 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_jql_tool 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_jql_tool 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_jql_tool. 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_jql_tool is provided by the Jira MCP Server MCP server (troylar/jira-mcp-server). 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 →