// SCAN REPORT

JIRA MCP Server

24 tools. 5 can modify or destroy data without limits.

5 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

5 can modify or destroy data

19 read-only

24 tools total

Community server · catalogue entry verified 02/07/2026

How to control JIRA MCP Server ↓

TOOL MAP

What JIRA MCP Server exposes to your agents

Read (19) Write / Execute (5) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous JIRA MCP Server tools

Write · Low jira_add_comment Adding a comment creates new data in JIRA but is fully reversible (comments can be edited or deleted). Write · Medium jira_create_issue This tool creates new data (JIRA issues) in a reversible manner. Write · Medium jira_transition_issue Transitioning an issue changes its workflow status (e.g., from 'To Do' to 'In Progress' to 'Done'), which modifies data in JIRA. Write · Medium jira_update_issue This tool creates or modifies data reversibly by updating issue metadata.

5 of JIRA MCP Server's 24 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control JIRA MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and JIRA MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "jira_add_comment": {
    "limits": [
      {
        "counter": "jira_add_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "jira_debug_search": {
    "limits": [
      {
        "counter": "jira_debug_search_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register JIRA MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON JIRA →

Instant setup, no code required.

FULL CATALOGUE

All 24 JIRA MCP Server tools

WRITE 5 tools

Write jira_add_comment Add a comment to a JIRA issue. Write jira_create_issue Create a new JIRA issue. Returns the created issue key and ID. Write jira_transition_issue Transition an issue to a new status. Use jira_get_transitions first to get valid transition IDs. Write jira_update_issue Update fields on a JIRA issue. Can update summary, description, assignee, priority, labels, and custom fields. Write jira_upload_attachment Upload a file as an attachment to a JIRA issue.

READ 19 tools

Read jira_debug_search Debug tool for exploring raw JIRA data. Returns raw field data and field name mappings. Useful for finding cus Read jira_download_attachment Download an attachment from JIRA to a local file path. Read jira_get_active_sprint Get the currently active sprint for a specific board. Returns sprint ID, name, dates, and goal. Read jira_get_backlog_stats Get aggregated statistics for issues matching a JQL query. Returns counts grouped by status, type, priority, a Read jira_get_create_fields IMPORTANT: Call this BEFORE creating an issue to discover required fields and their formats. Returns all requi Read jira_get_field_schema Get available JIRA fields with their IDs, names, and types. Useful for discovering custom field IDs (e.g., fin Read jira_get_issue Get detailed information about a specific JIRA issue by its key (e.g., PROJ-123). Returns all fields by defaul Read jira_get_issue_comments Get comments on a specific JIRA issue. Returns comment author, body, and creation date. Read jira_get_issue_history Get the changelog/history of a JIRA issue. Returns all field changes, status transitions, and other modificati Read jira_get_my_sprint_issues Get issues assigned to the current user in a specific sprint. Filters by assignee = currentUser(). Returns iss Read jira_get_sprint_issues Get all issues in a specific sprint. Returns issue keys, summaries, statuses, and assignees by default. Use th Read jira_get_sprint_report Generate a sprint report for retrospectives. Returns issue counts and story points grouped by status categorie Read jira_get_transitions Get available status transitions for an issue. Use this to see what statuses an issue can be moved to. Read jira_list_attachments List all attachments on a JIRA issue. Returns attachment IDs, filenames, sizes, and types. Read jira_list_boards List all accessible JIRA boards. Returns board IDs, names, types (scrum/kanban), and project keys. Read jira_list_field_values List discrete values for a JIRA field. Supports labels, priorities, statuses, issue types, resolutions, and co Read jira_list_sprints List sprints for a board or project. Returns sprint IDs, names, states, dates, and goals sorted by most recent Read jira_search_issues Search for issues using JQL (JIRA Query Language). Returns up to 50 issues by default. IMPORTANT: Queries must Read jira_search_users Search for JIRA users by name, email, or display name. Returns accountId which can be used for mentions or ass

FAQ

Questions about JIRA MCP Server

How do I prevent bulk modifications through JIRA MCP Server? +

The JIRA MCP Server server has 5 write tools including jira_add_comment, jira_create_issue, jira_transition_issue. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach JIRA MCP Server.

How many tools does the JIRA MCP Server MCP server expose? +

24 tools across 2 categories: Read, Write. 19 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on JIRA MCP Server? +

Register the JIRA MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every JIRA MCP Server tool call.

Deterministic rules across all 24 JIRA MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON JIRA →

Instant setup, no code required.

24 JIRA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.