jira_search_issues

Search Jira issues using JQL

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/jira-search-issues.md

WHAT IT DOES

What jira_search_issues does on ScopeGate

AI agents call jira_search_issues to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why jira_search_issues is rated Low

Searching for issues in Jira using JQL (Jira Query Language) is a read-only operation that retrieves and filters existing data. It has no side effects, does not create, modify, or delete data, and does not execute external commands. The blast radius of misuse is minimal—an attacker could only discover information already stored in Jira that they might not have authorization to see, but cannot alter or destroy data.

From the tool's definition Tool name 'jira_search_issues' and description 'Search Jira issues using JQL' indicate a query operation that retrieves data without modifying or deleting it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_search_issues safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_search_issues, this is the rule to start with:

jira_search_issues Allowed

jira_search_issues is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_search_issues": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every jira_search_issues call is checked against it from then on.

FAQ

Questions about jira_search_issues

What does the jira_search_issues tool do? +

Search Jira issues using JQL. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jira_search_issues? +

Register the ScopeGate 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 ScopeGate. Nothing to install.

What risk level is jira_search_issues? +

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

Can I rate-limit jira_search_issues? +

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.

How do I block jira_search_issues completely? +

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.

What MCP server provides jira_search_issues? +

jira_search_issues is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →