AI agents use create_issue to create or update resources in Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Server environment.
Creating a Jira issue modifies the Jira system state by adding a new record, which is a Write operation. While reversible via deletion, creating issues could generate unnecessary tickets, spam, or noise in project management systems if misused by an AI agent. Severity is medium because the blast radius is limited to the Jira workspace and the action is fully reversible, unlike destructive or financial operations.
From the tool's definition Tool name 'create_issue' and description 'Create a new Jira issue' indicate the tool creates new data in Jira that is reversible (issues can be deleted by the sibling tool 'delete_issue').
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 Jira MCP 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. It is categorised as a Write tool in the Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 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 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 Jira MCP Server MCP server (redhat-community-ai-tools/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira MCP 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.
30 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.