Create multiple issues in a single request. More efficient than creating one at a time.
AI agents use jira_batch_create_issues to create or update resources in Atlassian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian environment.
Creating issues in Jira is a reversible write operation (issues can be deleted afterward). The batch creation of multiple issues at once increases the blast radius compared to single-issue creation, as an agent could accidentally create many unwanted issues in a single call, but the operation itself remains reversible and does not permanently destroy data or commit financial transactions.
From the tool's definition Tool name and description explicitly state 'Create multiple issues' - this is a write operation that creates new data records in Jira.
Documented attack patterns abuse exactly the kind of access jira_batch_create_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_batch_create_issues:
{
"version": "1",
"default": "deny",
"tools": {
"jira_batch_create_issues": {
"limits": [
{
"counter": "jira_batch_create_issues_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}jira_batch_create_issues 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 multiple issues in a single request. More efficient than creating one at a time. It is categorised as a Write tool in the Atlassian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian MCP server in PolicyLayer and add a rule for jira_batch_create_issues: 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 Atlassian. Nothing to install.
jira_batch_create_issues 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_batch_create_issues 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_batch_create_issues. 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_batch_create_issues is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, 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.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.