search_issues
AI agents call search_issues 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.
The tool name 'search_issues' and context of a Jira integration indicate this retrieves or queries existing issues. Despite the empty description reducing confidence slightly, the naming convention and parallel to get_issue and list_projects (both Read operations) strongly suggest this is a query/search operation with no data modification capability.
From the tool's definition Tool named 'search_issues' with empty description; sibling tools include create_issue, update_issue, and add_comment which are Write/Execute operations. Search operations in issue tracking systems are read-only queries that retrieve data without side effects.
Attacks that exploit this kind of access
search_issues. 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 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 MCP Server. Nothing to install.
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 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 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.
search_issues is provided by the Jira MCP Server MCP server (jondoesflow/mcp_server_jira). 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 →