Introduce an admin‑configurable control that determines whether Atlassian Rovo MCP Server is allowed to create Jira issues in projects that have anonymous access enabled.
Today, when MCP is used against a Jira project that allows anonymous access, users see the error:
“This project is anonymous and can’t be used to create issues using Rovo MCP Server”
This is currently hard‑coded behavior for security reasons, with no way for admins to override it. The request is to add a toggle / configuration option so customers with valid use cases can explicitly allow MCP to create issues in such projects, while keeping the default secure.