AI agents call search_tickets to retrieve information from Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves ticket data without creating, modifying, or deleting any information. It is a standard search operation typical of Read category tools. Low severity as search operations have minimal blast radius—they only expose existing information without enabling destructive or financial actions.
From the tool's definition Tool name 'search_tickets' and description 'Search for tickets in specific projects using text search' indicate a read-only retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Search for tickets in specific projects using text search. It is categorised as a Read tool in the Jira MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP server in PolicyLayer and add a rule for search_tickets: 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. Nothing to install.
search_tickets 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_tickets 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_tickets. 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_tickets is provided by the Jira MCP server (taraskhust/jira-mcp-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 →