jira_search_issues
Search Jira issues with JQL (defaults to most recently updated).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jira-search-issues.md
What jira_search_issues does on UnClick
AI agents call jira_search_issues to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
jql | string | — | JQL query (e.g. 'project = ENG AND status = "In Progress"') |
site | string | Yes | Jira site (e.g. mycompany or mycompany.atlassian.net) |
email | string | Yes | Atlassian account email |
fields | string | — | Comma-separated fields to return |
api_token | string | Yes | Atlassian API token |
max_results | number | — | Issues to return (max 100, default 25) |
Parameters from the server's own tool schema.
Why jira_search_issues is rated Low
This tool retrieves/queries Jira issue data with no side effects. It falls squarely into the Read category. Severity is medium rather than low because Jira systems often contain sensitive business, technical, and project information; an AI agent with unrestricted search could leak confidential data, depending on the Jira instance's access controls.
From the tool's definition Tool name contains 'search' and description states 'Search Jira issues' with no mention of creation, modification, deletion, or execution. The tool queries and retrieves data using JQL.
Attacks that exploit this kind of access
The rule that runs jira_search_issues safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every jira_search_issues call is checked against it from then on.
Questions about jira_search_issues
Search Jira issues with JQL (defaults to most recently updated). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
jira_search_issues accepts 6 parameters: jql, site, email, fields, api_token, max_results. Required: site, email, api_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. Nothing to install.
jira_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 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.
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.
jira_search_issues is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue