Search issues via JQL. Requires bounded query.
AI agents call search_issues to retrieve information from Simple Jira MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from Jira using JQL (Jira Query Language) without creating, modifying, or deleting any data. The 'bounded query' requirement further suggests it is a read-only operation with limited scope. Severity is low because misuse would only expose existing issue information, not compromise data integrity or trigger external operations.
From the tool's definition Tool description states 'Search issues via JQL' and server description confirms it 'enabling them to search issues with JQL, retrieve detailed issue information'. The verb 'search' and action of querying/retrieving indicates no modifications or side effects.
Attacks that exploit this kind of access
Search issues via JQL. Requires bounded query. It is categorised as a Read tool in the Simple Jira MCP MCP Server, which means it retrieves data without modifying state.
Register the Simple Jira 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 Simple Jira MCP. 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 Simple Jira MCP server (timohaa/simple-jira-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 →