AI agents call jira_search_issues to retrieve information from Jira Dev 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 data from Jira without creating, modifying, or deleting any information. The description explicitly states it 'returns' results, indicating a passive data retrieval operation. Search and list operations are categorized as Read. The blast radius is minimal since misuse would only return information the user likely already has permission to access in Jira.
From the tool's definition Tool 'jira_search_issues' performs a search operation that returns issue keys, summaries, statuses, and assignees—classic read-only retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search Jira issues using natural language keywords or raw JQL. Returns issue keys, summaries, statuses, and assignees. It is categorised as a Read tool in the Jira Dev MCP Server, which means it retrieves data without modifying state.
Register the Jira Dev 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 Dev. 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 Dev MCP server (jira-dev-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 →