jira
8 Dtwo policies tagged "jira", including Force Internal Visibility on JSM Comments, JIRA: Block Change-History Actor Spoofing. Browse by what the control does rather than which app it targets.
Force Internal Visibility on JSM CommentsKeeps agent-drafted Jira Service Management (JSM) comments off the customer-facing portal by rewriting addCommentToJiraIssue calls to carry a restrictive…JIRA: Block Change-History Actor SpoofingBlocks any official Jira write call — transitionJiraIssue, editJiraIssue, or createJiraIssue — that carries a historyMetadata block, before it reaches the…JIRA: Cap Field and Result Exposure on ReadsNarrows the breadth of JIRA read requests before they run, on the two read surfaces that can pull large amounts of issue data into model context:JIRA: Deny Sensitive Project Search and ViewKeeps issues that belong to a configurable set of "sensitive" JIRA projects out of read access through the JIRA MCP server.JIRA: Freeze Destructive Issue OperationsFreezes the three irreversible Jira operations on the agent channel: jira delete issue, jira remove issue link, and jira remove watcher.JIRA: Protect Sensitive Projects from WritesBlocks write operations against issues that belong to a configurable set of "sensitive" JIRA projects.JIRA: Redact Sensitive Information from Issue ViewsRedacts sensitive content from the responses of JIRA issue-view tools before they reach the caller.JIRA: Role-Gated Writes (Read-Only Default)Makes Jira read-only by default on the MCP path.