Low Risk

search-tickets-jql

Search for jira tickets using custom JQL query

How to control search-tickets-jql ↓

What search-tickets-jql does on JIRA MCP

AI agents call search-tickets-jql to retrieve information from JIRA MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search-tickets-jql needs a policy

This tool searches and retrieves JIRA ticket data based on JQL (JIRA Query Language) parameters. It is purely informational—no tickets are created, modified, deleted, or have side effects triggered. The JQL syntax itself is restricted to read queries in standard JIRA implementations.

From the tool's definition Tool name 'search-tickets-jql' and description 'Search for jira tickets using custom JQL query' indicate a query/retrieval operation with no data modification.

Documented attack patterns abuse exactly the kind of access search-tickets-jql gives an agent:

How to control search-tickets-jql

PolicyLayer is an MCP gateway — it sits between your AI agents and JIRA MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search-tickets-jql:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search-tickets-jql": {}
  }
}

search-tickets-jql is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register JIRA MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search-tickets-jql

What does the search-tickets-jql tool do? +

Search for jira tickets using custom JQL query. It is categorised as a Read tool in the JIRA MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search-tickets-jql? +

Register the JIRA MCP server in PolicyLayer and add a rule for search-tickets-jql: 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. Nothing to install.

What risk level is search-tickets-jql? +

search-tickets-jql is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search-tickets-jql? +

Yes. Add a rate_limit block to the search-tickets-jql 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.

How do I block search-tickets-jql completely? +

Set action: deny in the PolicyLayer policy for search-tickets-jql. 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.

What MCP server provides search-tickets-jql? +

search-tickets-jql is provided by the JIRA MCP server (mankowskinick/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every JIRA MCP tool call.

Start from JIRA MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 JIRA MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.