Search Jira issues using JQL query
AI agents call searchJiraIssuesUsingJql to retrieve information from Atlassian Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves Jira issue data without modifying, deleting, or executing operations. While it is a Read operation, the severity is medium rather than low because: (1) JQL queries can be crafted to access sensitive issue information across workspaces (depending on permissions), (2) an AI agent could enumerate issues to identify sensitive projects or data, and (3) the multi-workspace context means a…
From the tool's definition Tool name is 'searchJiraIssuesUsingJql' and description states 'Search Jira issues using JQL query'. The verb 'search' and lack of any modification, deletion, or execution language indicate read-only data retrieval.
Attacks that exploit this kind of access
Search Jira issues using JQL query. It is categorised as a Read tool in the Atlassian Multi MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for searchJiraIssuesUsingJql: 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 Atlassian Multi. Nothing to install.
searchJiraIssuesUsingJql 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 searchJiraIssuesUsingJql 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 searchJiraIssuesUsingJql. 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.
searchJiraIssuesUsingJql is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-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 →