Create a new Jira issue with a summary, detailed description,
AI agents use create_issue to create or update resources in MCP JIRA Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP JIRA Server environment.
This tool creates new issues in JIRA, which modifies the system state reversibly. Issues can be edited or deleted by authorized users, making this a Write rather than Destructive action. The severity is medium because malicious creation of many false issues could disrupt workflows and team productivity, but the impact is remediable. Confidence is high as the intent is explicit in both name and description.
From the tool's definition Tool name 'create_issue' and description 'Create a new Jira issue' indicate creation of new data in JIRA. The description is incomplete but clearly shows a write operation that adds records to the system.
Documented attack patterns abuse exactly the kind of access create_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP JIRA Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_issue:
{
"version": "1",
"default": "deny",
"tools": {
"create_issue": {
"limits": [
{
"counter": "create_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Create a new Jira issue with a summary, detailed description,. It is categorised as a Write tool in the MCP JIRA Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP JIRA 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 MCP JIRA 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 MCP JIRA Server MCP server (warzuponus/mcp-jira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP JIRA Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 MCP JIRA Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.