jira_list_projects
List Jira projects, with an optional name query.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jira-list-projects.md
What jira_list_projects does on UnClick
AI agents call jira_list_projects 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 |
|---|---|---|---|
site | string | Yes | Jira site (e.g. mycompany) |
email | string | Yes | Atlassian account email |
query | string | — | Filter projects by name or key |
api_token | string | Yes | Atlassian API token |
max_results | number | — | Projects to return (max 100, default 50) |
Parameters from the server's own tool schema.
Why jira_list_projects is rated Low
This tool queries and retrieves existing Jira project metadata without creating, modifying, or deleting any data. It is purely informational retrieval with minimal blast radius if misused by an agent, as it cannot alter system state or expose sensitive data beyond what a legitimate user with project visibility would see.
From the tool's definition Tool name contains 'list' and description states 'List Jira projects' — a retrieval operation with no modification capability. The optional 'name query' parameter is a filter for read operations only.
Attacks that exploit this kind of access
The rule that runs jira_list_projects 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_list_projects, this is the rule to start with:
jira_list_projects 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_list_projects call is checked against it from then on.
Questions about jira_list_projects
List Jira projects, with an optional name query. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
jira_list_projects accepts 5 parameters: site, email, query, 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_list_projects: 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_list_projects 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_list_projects 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_list_projects. 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_list_projects 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