Critical-risk tools in Jira MCP Server
7 of the 57 tools in Jira MCP Server are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
confluence_delete_pageDestructiveDelete a Confluence page by ID.
-
confluence_delete_spaceDestructiveDelete a Confluence space by key. This is asynchronous on Confluence Cloud — the call returns a long-running task.
-
jira_delete_commentDestructiveDelete a comment from a Jira ticket. This action is irreversible.
-
jira_delete_ticketDestructiveDelete a Jira ticket. This action is IRREVERSIBLE. If the ticket has subtasks, set deleteSubtasks to true or the deletion will fail.
-
jira_remove_attachmentDestructiveRemove an attachment from a Jira ticket by attachment ID or filename. If using filename, fetches the ticket to find the attachment ID.
-
jira_remove_instanceDestructiveRemove a Jira instance configuration by name. Cannot remove the last remaining instance.
-
jira_unlink_ticketsDestructiveRemove a link between two Jira tickets. Fetches the issue to find the link ID automatically.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.