Create a new issue/task in Jira
AI agents use jira_create_issue to create or update resources in Jira MCP Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Integration environment.
This tool creates new data (issues/tasks) in Jira, which is a reversible write operation—issues can be deleted or updated later. It does not execute arbitrary code, delete data, or move money. While creation of project management items could have business implications if misused (spam, incorrect task creation affecting team workflows), the impact is limited to data creation rather than destruction or execution.
From the tool's definition Tool name is 'jira_create_issue' and description states 'Create a new issue/task in Jira', indicating irreversible creation of new data in a project management system.
Attacks that exploit this kind of access
Create a new issue/task in Jira. It is categorised as a Write tool in the Jira MCP Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira MCP Integration 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 Jira MCP Integration. 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 Jira MCP Integration MCP server (koveh/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →