jira_search_issues
AI agents call jira_search_issues to retrieve information from MCP JIRA Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'search' operation in the name and context of JIRA tools indicates data retrieval without side effects. Search tools query existing data and return results without creating, modifying, or deleting anything. Even without a description, the naming convention and position among sibling tools that handle creation, updates, transitions, and deletion strongly suggest this is a read-only query operation.
From the tool's definition Tool name is 'jira_search_issues' which performs a search operation; no description provided but the sibling tools include destructive actions (jira_delete_issue, jira_update_issue) that are distinct from this one, indicating jira_search_issues is read-only.
Attacks that exploit this kind of access
jira_search_issues. It is categorised as a Read tool in the MCP JIRA Server MCP Server, which means it retrieves data without modifying state.
Register the MCP JIRA Server 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 MCP JIRA Server. 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 MCP JIRA Server MCP server (tarangbhavsar/mcp-jira-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 →