create_monthly_tasks · Jira MCP: Risk & Policy

WHAT IT DOES

What create_monthly_tasks does on Jira

AI agents use create_monthly_tasks 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 create_monthly_tasks needs a policy

This tool creates multiple Jira tasks in bulk from configuration files. While task creation is reversible (tasks can be deleted), the blast radius is high because an AI agent could inadvertently create large numbers of tasks across projects, causing clutter and confusion. The tool accepts a filter parameter for project scope, and the dry-run default mitigates some risk, but when executed it performs Write operations.

From the tool's definition Tool description states it 'create[s] the tasks' and accepts an 'execute=true' parameter to 'actually create the tasks', indicating reversible data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_monthly_tasks Rate-limited

create_monthly_tasks 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": {
    "create_monthly_tasks": {
      "limits": [
        {
          "counter": "create_monthly_tasks_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 create_monthly_tasks

What does the create_monthly_tasks tool do? +

Run all monthly_admin.json bulk task configs from ~/.softspark/jira-mcp/templates/tasks/<KEY>/. Defaults to dry-run. Set execute=true to actually create the tasks. Optionally filter to a single project key. 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 create_monthly_tasks? +

Register the Jira MCP server in PolicyLayer and add a rule for create_monthly_tasks: 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 create_monthly_tasks? +

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

Can I rate-limit create_monthly_tasks? +

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

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

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