jira_create_issue
Create a Jira issue. project_key can be filled from a saved memory default.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jira-create-issue.md
What jira_create_issue does on UnClick
AI agents use jira_create_issue to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
site | string | Yes | Jira site (e.g. mycompany) |
email | string | Yes | Atlassian account email |
summary | string | Yes | Issue summary / title |
api_token | string | Yes | Atlassian API token |
issue_type | string | — | Issue type name (default Task) |
description | string | — | Plain-text description |
project_key | string | — | Project key (e.g. ENG). Can be a saved default. |
Parameters from the server's own tool schema.
Why jira_create_issue is rated Medium
Creating a Jira issue modifies project state by adding a new record, but this is not destructive since issues can be deleted or archived. It is not Execute (no code/command execution), Financial, or Destructive. The severity is medium because misuse could create many unwanted issues causing operational noise and project management disruption, but the impact is bounded and reversible.
From the tool's definition Tool name 'jira_create_issue' and description 'Create a Jira issue' explicitly state the action creates a new issue in Jira, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs jira_create_issue 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_create_issue, this is the rule to start with:
jira_create_issue stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_issue call is checked against it from then on.
Questions about jira_create_issue
Create a Jira issue. project_key can be filled from a saved memory default. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
jira_create_issue accepts 7 parameters: site, email, summary, api_token, issue_type, description, project_key. Required: site, email, summary, 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_create_issue: 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_create_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jira_create_issue 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_create_issue. 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_create_issue 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