// SCAN REPORT

Atlassian

51 tools. 25 can modify or destroy data without limits.

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

Last updated: 12 Jun 2026

25 can modify or destroy data

26 read-only

51 tools total

Community server · catalogue entry verified 12/06/2026

How to control Atlassian ↓

TOOL MAP

What Atlassian exposes to your agents

Read (26) Write / Execute (20) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Atlassian tools

Destructive · High confluence_delete_page This tool performs irreversible deletion of Confluence pages. Destructive · High jira_delete_board This tool irreversibly deletes a Jira board and all associated configuration, which cannot be recovered. Destructive · High jira_delete_issue This tool permanently deletes Jira issues, which is an irreversible operation that destroys data and cannot be recovered except through trash recovery (if available). Destructive · High jira_delete_sprint This tool irreversibly deletes sprint data, which is a permanent destructive action.

25 of Atlassian's 51 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Atlassian

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

Deny destructive operations

{
  "confluence_delete_page": {
    "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

{
  "jira_link_to_epic": {
    "limits": [
      {
        "counter": "jira_link_to_epic_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "confluence_get_comments": {
    "limits": [
      {
        "counter": "confluence_get_comments_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 Atlassian — 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 ATLASSIAN →

Free to start. No card required.

FULL CATALOGUE

All 51 Atlassian tools

DESTRUCTIVE 5 tools

Destructive confluence_delete_page Delete a page. By default, moves to trash. Use purge option for permanent deletion. Destructive jira_delete_board Delete a board. Warning: This is permanent and cannot be undone. All board configuration will be lost. Destructive jira_delete_issue Delete a Jira issue. This action cannot be undone unless the issue is in the trash. Destructive jira_delete_sprint Delete a sprint. Note: Can only delete sprints that have not been started (future state). Cannot delete active Destructive jira_remove_issue_link Remove/delete a link between two issues. Requires the link ID.

WRITE 20 tools

Write jira_link_to_epic Link multiple issues to an epic. Creates Epic-Story links between issues and epic. Write jira_rank_backlog_issues Rank/reorder issues in the backlog. Used to adjust issue priority order before sprint planning. Specify either Write confluence_add_comment Add a footer comment to a page. Can be a top-level comment or a reply to another comment. Write confluence_add_label Add one or more labels to a page. Labels help organize and categorize content. Write confluence_create_page Create a new page in Confluence. Requires space ID, title, and content in storage format. Write confluence_update_page Update an existing Confluence page. Requires page ID, new title, and content. Write jira_add_comment Add a comment to a Jira issue. Comments support plain text. Write jira_add_worklog Add a worklog entry to an issue. Records time spent working on the issue. Write jira_batch_create_issues Create multiple issues in a single request. More efficient than creating one at a time. Write jira_batch_create_versions Create multiple versions/releases in a project. More efficient than creating one at a time. Write jira_create_board Create a new agile board (Scrum or Kanban). The board can be created for a specific project or based on a filt Write jira_create_issue Create a new Jira issue with full hierarchy support. Supports Epic, Story, Task, Bug, and Sub-task with parent Write jira_create_issue_link Create a link between two issues. Use jira_get_issue_link_types to see available link types. Write jira_create_sprint Create a new sprint on a board. Requires board ID, sprint name, and optional dates. Write jira_create_version Create a new version/release in a project. Used for release management. Write jira_move_issues_to_sprint Move issues to a sprint. This is essential for sprint planning - add issues from backlog to sprint. Write jira_transition_issue Transition an issue to a new status. Requires a valid transition ID from jira_get_transitions. Write jira_update_board Update an existing board. Can modify board name or filter. Note: Cannot change board type. Write jira_update_issue Update an existing Jira issue. Can modify summary, description, parent, and other fields. Write jira_update_sprint Update an existing sprint. Can modify name, dates, goal, or state (start/close sprint).

READ 26 tools

Read confluence_get_comments Get footer comments on a page. Returns comments with their content and metadata. Read confluence_get_labels Get labels attached to a page. Returns label names and prefixes. Read confluence_get_page Get a single page by ID with detailed information. Supports single body format. Read confluence_get_page_children Get child pages of a specific page. Returns a list of direct children. Read confluence_list_pages List pages in a Confluence space. Returns page titles, IDs, and metadata. Read confluence_list_spaces List all Confluence spaces. Returns space keys, names, and types. Read confluence_search Search Confluence content using CQL (Confluence Query Language). Returns matching pages, blog posts, and other Read confluence_search_user Search for users using CQL. Returns user information including account ID, display name, and email. Read jira_batch_get_changelogs Batch get changelogs for multiple issues. Returns complete change history for each issue. Read jira_download_attachments Get attachment information including download URL. Returns attachment metadata and content URL. Read jira_get_agile_boards Get all agile boards. Can filter by project. Returns board names and types. Read jira_get_backlog_issues Get all issues in the backlog for a board. Returns issues that are not assigned to any sprint. Read jira_get_board_issues Get all issues on a specific board. Can filter with JQL. Returns issue keys and summaries. Read jira_get_epic_issues Get all issues (stories, tasks, bugs) that belong to an epic. Returns child issues of the epic. Read jira_get_issue Get detailed information about a single Jira issue by its key. Returns all issue fields. Read jira_get_issue_link_types Get all available issue link types. Returns link type names, inward/outward descriptions. Read jira_get_project_issues Get all issues for a specific project. Returns issues ordered by creation date. Read jira_get_project_versions Get all versions/releases for a project. Returns version names, release dates, and status. Read jira_get_sprint_issues Get all issues in a specific sprint. Returns issue details and status. Read jira_get_sprints_from_board Get all sprints from a board. Can filter by state (active, future, closed). Returns sprint names and dates. Read jira_get_transitions Get available workflow transitions for an issue. Returns transition IDs and names that can be used to change i Read jira_get_user_profile Get user profile information by account ID. Returns display name, email, and avatar. Read jira_get_worklog Get all worklog entries for an issue. Returns time spent, author, and dates. Read jira_list_projects List all Jira projects accessible to the user. Returns project keys, names, and types. Read jira_search_fields Search for custom fields in Jira. Returns field IDs, names, and schemas. Read jira_search_issues Search for Jira issues using JQL (Jira Query Language). Returns issue keys, summaries, and fields.

EXPLORE

Related servers

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

FAQ

Questions about Atlassian

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

Yes. The Atlassian server exposes 5 destructive tools including confluence_delete_page, jira_delete_board, jira_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 Atlassian? +

The Atlassian server has 20 write tools including jira_link_to_epic, jira_rank_backlog_issues, confluence_add_comment. 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 Atlassian.

How many tools does the Atlassian MCP server expose? +

51 tools across 3 categories: Destructive, Read, Write. 26 are read-only. 25 can modify, create, or delete data.

How do I enforce a policy on Atlassian? +

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

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

ENFORCE POLICY ON ATLASSIAN →

Free to start. No card required.

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