Add "Always Allow" (persistent per-session approval) for read-only Atlassian Rovo MCP tools

XMLWordPrintable

      Summary

      When the Atlassian Rovo MCP connector is integrated with Claude (Anthropic), every tool call from the connector requires manual approval within each conversation — even for read-only operations such as getJiraIssue, getConfluencePage, search, and searchJiraIssuesUsingJql.

      Problem Other MCP connectors (for example Slack) support an "Always Allow" option that persists approval for repeated tool calls within a session. The Atlassian Rovo MCP connector does not appear to offer this for read-only tools, so users must re-approve the same type of request multiple times per conversation — sometimes up to 6 times in a single prompt.

      This creates a significant usability problem: users have to actively monitor and approve each step instead of letting the assistant complete a multi-step task end to end. It particularly affects multi-step workflows (e.g. "summarize this epic and its linked issues"), which fan out into many individual read calls.

      Request

      Please enable "Always Allow" (or equivalent persistent approval) for read-only Rovo MCP tools, consistent with how other connectors behave. Write-capable tools should continue to require per-call approval — this request is specifically limited to read-only operations.

              Assignee:
              Unassigned
              Reporter:
              Diego Larangeira
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: