batch_create_versions · MCP Atlassian MCP: Risk & Policy

WHAT IT DOES

What batch_create_versions does on MCP Atlassian

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

WHY IT NEEDS A POLICY

Why batch_create_versions needs a policy

Creating versions in Atlassian products (Jira/Confluence) typically involves adding metadata or release information—reversible operations that modify data without deletion. This falls under Write category. Severity is medium because batch operations could create many versions, potentially cluttering systems or consuming storage, but can be undone through deletion/modification.

From the tool's definition Tool name 'batch_create_versions' indicates creation of multiple version objects. The 'batch' prefix suggests bulk operations. No description provided, limiting evidence specificity.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_create_versions Rate-limited

batch_create_versions 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_versions": {
      "limits": [
        {
          "counter": "batch_create_versions_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 MCP Atlassian, so you can run agents against it safely.

FAQ

Questions about batch_create_versions

What does the batch_create_versions tool do? +

batch_create_versions. It is categorised as a Write tool in the MCP Atlassian 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_versions? +

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

What risk level is batch_create_versions? +

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

Can I rate-limit batch_create_versions? +

Yes. Add a rate_limit block to the batch_create_versions 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_versions completely? +

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

batch_create_versions is provided by the MCP Atlassian MCP server (lklkxcxc/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.