Create a new Jira issue with optional fields.
AI agents use create_issue to create or update resources in AI-Powered Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI-Powered Jira MCP Server environment.
Creating a new Jira issue is a reversible write operation that modifies project state by adding data. It does not execute arbitrary code, delete data, or move money. However, it has medium severity because malicious agents could spam issues, pollute project backlogs, or create misleading tickets that affect team workflow and decision-making.
From the tool's definition Tool description states 'Create a new Jira issue' — this creates new data in Jira. The sibling tool context (add_comment, change_status, create_project, search_issues) confirms this is a write-oriented operation within project management workflows.
Attacks that exploit this kind of access
Create a new Jira issue with optional fields. It is categorised as a Write tool in the AI-Powered Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AI-Powered Jira MCP Server MCP server in PolicyLayer and add a rule for 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 AI-Powered Jira MCP Server. Nothing to install.
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 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 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.
create_issue is provided by the AI-Powered Jira MCP Server MCP server (vkhanna2004/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 →