// SCAN REPORT

Jira

37 tools. 15 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

15 can modify or destroy data

22 read-only

37 tools total

Community server · catalogue entry verified 30/06/2026

How to control Jira ↓

TOOL MAP

What Jira exposes to your agents

Read (22) Write / Execute (10) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Jira tools

Destructive · High delete_all_comments This tool permanently removes all comments associated with a ticket, which cannot be undone. Destructive · High delete_comment This tool permanently removes a comment, which cannot be undone. Destructive · High delete_issue Deleting a Jira ticket is an irreversible action that removes project tracking data and cannot be undone through normal means. Destructive · High delete_worklog This tool permanently removes worklog entries from Jira tickets.

15 of Jira's 37 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

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

Deny destructive operations

{
  "delete_all_comments": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_comment": {
    "limits": [
      {
        "counter": "add_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_agile_boards": {
    "limits": [
      {
        "counter": "get_agile_boards_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 — 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 37 Jira tools

DESTRUCTIVE 5 tools

Destructive delete_all_comments Delete all comments from a Jira ticket Destructive delete_comment Delete a comment from a Jira ticket Destructive delete_issue Delete a Jira ticket Destructive delete_worklog Delete a worklog from a Jira ticket Destructive remove_issue_link Remove a link between two Jira issues

WRITE 10 tools

Write add_comment Add a comment to a Jira ticket. Supports mentions using [~accountId] or [~email@example.com] format. Write add_worklog Add worklog (time spent) to a Jira ticket Write assign_ticket Assign a Jira ticket to a user Write batch_create_issues Create multiple Jira issues in a batch Write create_issue_link Create a link between two Jira issues Write create_ticket Create a new Jira ticket Write create_version Create a new version in a project Write update_status Update the status of a Jira ticket Write update_ticket_fields Update fields of a Jira ticket (e.g., original estimate, story points, labels, assignee, priority, due date, e Write update_worklog Update an existing worklog on a Jira ticket

READ 22 tools

Read get_agile_boards Get all Agile boards for a project Read get_all_projects Get all Jira projects Read get_available_fields Get all available fields for a Jira ticket with their metadata and field IDs. Returns a mapping of field names Read get_board_issues Get issues from an Agile board Read get_comments Get comments for a specific Jira ticket Read get_kb_page Get a Confluence/KB page by page ID or full URL. Returns page title, space, content (as plain text), version, Read get_kb_page_children Get child pages of a Confluence/KB page. Useful for navigating page hierarchies. Read get_kb_page_comments Get comments on a Confluence/KB page Read get_kb_spaces List available Confluence/KB spaces. Useful for discovering space keys before searching. Read get_project_issues Get all issues for a specific project Read get_project_versions Get all versions for a project Read get_sprint_issues Get issues from a sprint Read get_sprints_from_board Get all sprints from an Agile board Read get_ticket Get details of a specific Jira ticket Read get_ticket_fields Get all available fields and their metadata for a Jira ticket (useful for finding custom field IDs) Read get_transitions Get available transitions for a Jira ticket Read get_user_profile Get user profile information Read get_worklog Get worklogs for a specific Jira ticket Read list_tickets List Jira tickets assigned to you Read search_kb_pages Search for Confluence/KB pages by text, title, or CQL query. Returns matching pages with titles, spaces, and U Read search_tickets Search for tickets in specific projects using text search Read search_users Search for Jira users by email or display name to get their accountId for mentions

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Jira

Can an AI agent delete data through the Jira MCP server? +

Yes. The Jira server exposes 5 destructive tools including delete_all_comments, delete_comment, delete_issue. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Jira? +

The Jira server has 10 write tools including add_comment, add_worklog, assign_ticket. 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.

How many tools does the Jira MCP server expose? +

37 tools across 3 categories: Destructive, Read, Write. 22 are read-only. 15 can modify, create, or delete data.

How do I enforce a policy on Jira? +

Register the Jira 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 tool call.

Deterministic rules across all 37 Jira tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON JIRA →

Instant setup, no code required.

37 Jira tools catalogued and risk-classified — across an index of 43,000+ MCP servers.