jira_create_subtask · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_create_subtask does on Jira MCP Server

AI agents use jira_create_subtask 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.

WHY IT NEEDS A POLICY

Why jira_create_subtask needs a policy

This is a Write operation because it creates and persists new data (a subtask) in Jira, which is reversible (subtasks can be deleted). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.

From the tool's definition Tool description states 'Create a subtask under a parent Jira ticket.' The verb 'create' indicates data creation. The tool modifies Jira's state by adding a new subtask entity linked to a parent ticket.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_create_subtask Rate-limited

jira_create_subtask 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": {
    "jira_create_subtask": {
      "limits": [
        {
          "counter": "jira_create_subtask_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_create_subtask

What does the jira_create_subtask tool do? +

Create a subtask under a parent Jira ticket. The subtask is created in the same project as the parent. NEVER use em dashes or en dashes in text fields. 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.

How do I enforce a policy on jira_create_subtask? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_create_subtask: 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.

What risk level is jira_create_subtask? +

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

Can I rate-limit jira_create_subtask? +

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

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

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