batch_create_issues · Jira MCP: Risk & Policy

WHAT IT DOES

What batch_create_issues does on Jira

AI agents use batch_create_issues to create or update resources in Jira — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira environment.

WHY IT NEEDS A POLICY

Why batch_create_issues needs a policy

This tool creates new Jira issues, which is a write operation that modifies data (adds new tickets to a project). It is reversible (issues can be deleted later), so it does not qualify as Destructive. The batch nature means multiple issues could be created at once, increasing blast radius slightly, but the operation is still fundamentally a Write category action.

From the tool's definition Tool name is 'batch_create_issues' and description states 'Create multiple Jira issues in a batch'. The 'create' verb and context of creating Jira issues indicates data creation/modification without irreversible deletion.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_create_issues Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_create_issues": {
      "limits": [
        {
          "counter": "batch_create_issues_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jira, so you can run agents against it safely.

FAQ

Questions about batch_create_issues

What does the batch_create_issues tool do? +

Create multiple Jira issues in a batch. It is categorised as a Write tool in the Jira MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_create_issues? +

Register the Jira MCP server in PolicyLayer and add a rule for 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 Jira. Nothing to install.

What risk level is batch_create_issues? +

batch_create_issues is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit batch_create_issues? +

Yes. Add a rate_limit block to the 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.

How do I block batch_create_issues completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides batch_create_issues? +

batch_create_issues is provided by the Jira MCP server (taraskhust/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.